By name: release-extension description: Cut a new Celestia Chrome extension release — assess whether a release is warranted, decide the semver bump and write end-user release notes, then build, zip, tag, and create the GitHub release after one human approval. The Chrome Web Store upload stays manual. Use when the user wants to release a new version, cut a release, ship a new extension version, or asks "do we need a release?".
Release
Drive a Celestia extension release end to end. You make the judgment calls (whether to release, the version bump, the notes); the human approves once; the Chrome Web Store upload stays in their hands.
The full runbook is docs/agents/release.md — the single source of truth,
shared with Codex. Follow it exactly. The phases are:
- Assess — commits since the last
vX.Y.Ztag; if nothing user-facing shipped, stop and report "no release needed". - Propose — semver bump + end-user release notes; wait for the human's approval before writing, committing, building, or tagging anything.
- Apply — hard-block on
pnpm typecheck && pnpm test, bumpmanifest.config.ts, commit,pnpm build, drift-guard the built manifest, zipdist/tocelestia-chrome-extension-vX.Y.Z.zip. - Publish — tag, push (rebase-only
main),gh release createwith notes- zip.
- Hand off — print the manual Chrome Web Store upload checklist and stop.
Do not automate the Chrome Web Store upload.