feat: update extension changelog and disabled-site management by hoangsvit · Pull Request #82 · ePlus-DEV/gmail-alias-toolkit

hoangsvit · 2026-07-23T17:09:08Z

Summary

update the in-extension changelog through v1.3.2 without modifying CHANGELOG.md;
update extension metadata to v1.3.2;
resolve the /web version from the latest published GitHub Release at build time;
replace the unbounded disabled-site list rendering with search and 5-item pagination;
add regression coverage for disabled-site filtering, version hardcoding, and GitHub release resolution.

Version handling

The extension and website now use the appropriate source for their context:

the installed extension prefers browser.runtime.getManifest().version;
src/version.ts falls back to the root package.json version;
the /web Vite build requests GitHub releases/latest, normalizes tags such as v1.3.2, and injects that published version into APP_VERSION;
when GitHub is unavailable, has no release, or returns an invalid tag, the web build safely falls back to root package metadata;
Pages and PR-preview builds authenticate the release request with GITHUB_TOKEN to avoid public API rate limits.

Version strings inside the in-extension changelog remain intentional historical release data. web/package.json remains the private web workspace package version and is not used as the extension version.

Disabled-site behavior

The previous list only used a fixed-height scroll container, so every stored site was still rendered. The new panel:

shows five sites per page;
renders only the current page;
provides previous and next navigation;
supports normalized hostname search when the list contains more than five sites;
automatically returns to a valid page after filtering or re-enabling a site.

Testing

GitHub Actions workflow validation
TypeScript compile
Unit tests, including GitHub release success and fallback cases
Production extension build
Production manifest-scope verification
Website build
CodeRabbit

Notes

CHANGELOG.md is intentionally unchanged.

qodo-code-review · 2026-07-23T17:09:14Z

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

eplus-bot · 2026-07-23T17:09:16Z

Thank you for creating this pull request and helping make the project better.

We will review / merge it when we are online.

coderabbitai · 2026-07-23T17:09:17Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e375f7ee-842d-4e56-8442-9b9fe2b76867

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch feat/update-extension-changelog-sites-pagination

_{Comment @coderabbitai help to get the list of available commands.}

eplus-bot · 2026-07-23T17:24:09Z