Skip to content
Changelog
Phase 11v0.1.0Unreleased

Continuous deployment

Completed

Pushing to main now builds, verifies and deploys the companion site; pushing a tag builds the release and publishes it on GitHub. The extension itself is unchanged.

This phase is in the source repository but has not been published to the Chrome Web Store.

Highlights

  • CI on every push and pull request: security scan, typecheck, tests, build and a check of the built site. It never deploys or publishes.
  • Pushing to main deploys the website to Hostinger over FTPS, then verifies the live site. Files the deploy did not put there, such as .well-known, are left alone.
  • A pushed v* tag runs the release builder and publishes a GitHub Release with the extension zip, website bundle, store package, reports and checksums. Nothing goes to the Chrome Web Store.
  • /health and /release.json report the live version, commit and build time; the changelog shows which build of the site you are reading.
  • Every release includes a validated Chrome Web Store submission package with an upload checklist, and a website bundle for manual upload or rollback.
  • A security scan fails the build on committed credentials, .env files, localhost URLs, the placeholder domain, sourcemaps, oversized assets or duplicate permissions.
  • Bundler runs and store captures are cached on their inputs: a release with nothing changed takes about 8 seconds instead of about 50.

Fixes

  • The placeholder domain was still compiled into the site bundle as an unused fallback even with VITE_SITE_URL set; the new site verification caught it, and it now folds away at build time.

Breaking changes

None.

Migration notes

  • None for users. To deploy, set HOSTINGER_HOST, HOSTINGER_USER and HOSTINGER_PASS as repository secrets.