1 Commits
Author SHA1 Message Date
raucao 66e58c49da Cut and publish extension releases from the version lifecycle
Releases were built and signed in CI, which meant AMO credentials had to
live on the runner. Move the whole flow local: builds and Firefox signing
happen on the maintainer's machine and only the finished artifacts are
published.

Add `ext:pack:firefox` and `ext:pack:chrome` (production builds; the
Firefox one is signed via `web-ext sign` unlisted with credentials read
from the GNOME Keyring through `secret-tool`, the Chrome one is zipped)
and wire them to the `version` lifecycle:

- `preversion` runs lint and tests.
- `version` builds and signs into `web-ext-artifacts/`.
- `postversion` pushes the bump commit and tag, then uploads both
  artifacts to the Gitea release and publishes it if still a draft.

Switch the plain `ext:build:*` scripts to production and add
`ext:build:dev:*` for development builds; `ext:dev` is unchanged. The
build manifest now takes its version from package.json and drops the
"(dev)" name suffix when `DASHTAB_RELEASE=1`.

Because packaging needs a production build, relax the AGENTS.md
production-build restriction to allow it for packaging and releasing.
2026-11-10 12:14:14 +04:00