- ci.yml: the Firefox package is built and checked beside the Chrome one.
- release.yml: three release files — the Chromium package (Chrome Web Store
and Edge Add-ons), the Firefox package and AMO's sources archive — each
staged by exact name so a missing one fails the run, both manifests checked
against the tag, SHA256SUMS over all three.
- One store job per store (docs/12 §3), each off until its repo variable is
true, each in its own GitHub Environment holding only its own secrets, each
checking the downloaded file against SHA256SUMS before uploading. They
install tools/publish — publish-browser-extension 6.2.0 and its three
dependencies, from their own lockfile, scripts off — instead of the ~320
packages of the dev toolchain, which the single old job installed next to
four Chrome secrets.
- The old job could not have worked: it sent CWS API v1.1 credentials, and
v1.1 was shut down on 2026-10-15. store-chrome uses v2 (publisher id and a
service account) and sets CHROME_API_VERSION explicitly. store-firefox is
listed and desktop-only; store-edge sends the Chromium package.
- Dependabot watches tools/publish; the licence gate reads its lockfile too.
- qodana.yaml: clean since the first run's findings were handled, so any new
one now fails that (non-required) workflow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>