Maintainers

Release once, publish with confidence.

The release workflow validates a tagged source revision, builds the root-layout Chrome ZIP, creates a GitHub Release, and can submit an existing Store item through Google's API.

Automated releases

Push a version tag in the form vX.Y.Z after merging the matching version and changelog update to main. GitHub Actions type-checks, tests, builds, validates, packages, retains the ZIP, and creates or updates the matching GitHub Release.

Chrome Web Store automation

The first Store item must be configured manually. Later releases can upload and publish only when trusted maintainers configure the chrome-web-store GitHub Environment secrets and enable the publish variable. Chrome review and visibility still control when the update becomes public.

Official runbook

The repository's HOWTO has every account, API credential, GitHub Actions secret, versioning, tag, manual review, and custom-domain step. The shorter release guide is useful during routine maintenance.

Website deployment

Changes under website/ on main deploy through GitHub Actions to GitHub Pages. The site has only relative internal links, so GitHub's project URL and a future submate.ghassen.io custom domain use the same build.