releaselisted
Install: claude install-skill wilfison/ai-usagebar
# Release a new ai-usagebar version
This extension's release touches **two version fields, a changelog, a commit, and
an annotated tag**, then pushes both the commit and the tag. The tag push
triggers `.github/workflows/release.yml`, which re-runs the CI gates, packs the
zip, and publishes the GitHub release, the only distribution channel (the
extension is not on extensions.gnome.org). That workflow fails if the tag does
not match `version-name` in `metadata.json`, so follow the steps in order and
confirm the numbers before anything irreversible.
The push at the end is the only hard-to-undo step; everything before it is local
and safe to redo. Treat the work before the push as freely revisable, and stop
for an explicit OK at the push gate.
## Step 0: Preflight (never release a broken or dirty tree)
Run these and stop if any fails; a release should snapshot a known-good state:
1. **Right branch, clean tree, synced with remote.** Confirm you're on `main`
with `git status`. If there are uncommitted changes, surface them and ask
whether to commit, stash, or abort; don't bundle stray edits into the release
commit. Run `git fetch` and make sure `main` isn't behind `origin/main`.
2. **CI gates pass locally.** These mirror the gates in `release.yml`; a tag
that fails any of them is pushed but never gets a release:
```bash
make test && make lint && make eslint && make validate && make i18n-check && make pack
```
`make eslint` needs `npm ci` once; `make pac