AGENT SKILL

release

暂无简介

License 许可
MIT
最近更新
2026-11-15
Stars
★ 3
Forks
3

03 SKILL.md 正文

Only a release reaches production: develop integrates without full CI (/repo:merge), the release runs every check. Git Flow: release/vX.Y.Z from develop takes only fixes, merges into main (tag vX.Y.Z) and back into develop. Urgent production fix: same path from main's latest tag, on hotfix/vX.Y.Z.

Read first the project's CLAUDE.md ([RELEASES] or "Releases"): announcement (what's-new, email), deployment commands, extra checks. Stop if no production main. Talk in the user's language. Never switch the main tree's branch: each in .claude/worktrees/<name> (release-vX.Y.Z, main).

ion-repo's own repo

No production: the tag publishes. These replace the steps below.

  1. ion repo version: candidates, proposed number, plan tickets still open.
  2. ion repo version cut (--minor for a milestone decided by its owner): branch release/vX.Y.Z in .claude/worktrees/release-vX.Y.Z, CHANGELOG.md drafted, numbers bumped. Rewrite the entry for users (breaking first, each with its conversion by ion repo update; keep - **After updating**: … lines, which become backlog tickets), delete the draft line, commit; ion repo version cut again: full checks, tag -rc.N pushed. Candidate fix: fix: commit, cut again.
  3. ion repo version promote when ion repo version says ready (--urgent only if its owner asks: no soak nor repo, green CI still required): tag on its exact commit, merged into main and develop; pypi.yml publishes package and GitHub Release.
  4. ion repo update --all only with the user's yes.

1. Choose

  • git fetch origin --tags. Previous: git describe --tags --abbrev=0 origin/main.
  • Candidate: argument, else origin/develop. Urgent fix: latest tag plus only the fix's commits (git cherry-pick).
  • Number: argument, else project's CLAUDE.md (ion-repo: next patch, breaking included, minor only for an owner-decided milestone; ion repo version proposes), else semver as vX.Y.Z, never v2: next minor with feat, next patch with only fixes, next major only for a breaking change after 1.0; the first release is v0.1.0.
  • Changes: git log --first-parent --format='%h %s' <previous>..<candidate>. Work left out: take an older candidate, don't undo code on the release.
  • /repo:review --repo. The release note says clearly what a poor subject hides.

2. Cut

git worktree add .claude/worktrees/release-vX.Y.Z -b release/vX.Y.Z <candidate>, git push -u origin release/vX.Y.Z. Then only fix: commits, never a feature.

3. Risks since previous release

  • Migrations (*/migrations/): schema, data, reversible? Deployment applies after backup; flag irreversible.
  • Settings: new env variables (config(, runtimeConfig, .env.example); check they exist in production before deploying.
  • API contract: routes or fields removed or renamed in openapi.json; a cached front calls the old one. Deploy API, then front.
  • Flags: features shipped off, planned production state.
  • Dependencies added or major-bumped.

4. Announcement

Per CLAUDE.md, which keeps where it goes and how it is sent. Check it exists for vX.Y.Z, describes the risks found, promises neither work left out nor a feature behind a flag staying off. Otherwise write it on the release: through /words:announce vX.Y.Z when the words plugin is installed (claude plugin list), else by hand; either way have the user approve the text.

5. Full checks

ion repo ci release/vX.Y.Z (or GitHub CI on the branch): every job. Failure: fix on the release, commit, rerun until green. Report jobs not replayed.

6. Go-ahead

Show briefly: number, changes, risks, announcement, CI verdict, rollback (previous release). Wait for agreement: this is production.

7. Merge and tag

git worktree add .claude/worktrees/main main
git -C .claude/worktrees/main merge --no-ff release/vX.Y.Z -m "Release vX.Y.Z: <summary>"
git -C .claude/worktrees/main tag -a vX.Y.Z -m "Release vX.Y.Z" -m "<changes, one line each>"
git push origin main vX.Y.Z && git worktree remove .claude/worktrees/main

main's commit holds the release's files: the deploy script accepts its ion repo ci verdict (green-ci.sh), no CI replay.

8. Deploy

Project's commands (often scripts/ops/deploy-backend.sh --dry-run, then without, then deploy-frontend.sh; dashboard alone: deploy-frontend.sh only), API before front. Then check: script's smoke test, production logs a few minutes (project's diagnosis skill if any), announcement visible. Breakage: back to the previous release via the project's procedure, and say so. No deployment (no scripts/ops/deploy-*.sh, nothing in CLAUDE.md): release ends at the tag on main; say so, go to step 9. PyPI command (.github/workflows/pypi.yml, ion repo set pypi_name=…): pushed tag deploys, version X.Y.Z from vX.Y.Z. gh run watch, then check https://pypi.org/project/<pypi_name>/X.Y.Z/; a red run names its step. First tag needs either a PYPI_TOKEN secret in the pypi environment ("Entire account" to create the project, /repo:token), or a publisher on https://pypi.org/manage/account/publishing/ (repository, workflow pypi.yml, environment pypi). A PyPI version can never be re-uploaded: fix a broken one with the next tag.

Actions blocked (billing): don't wait on a queued run, whose job can sit for minutes before the refusal shows in its annotations; gh run cancel it, so it cannot publish later, and publish from the machine. The repo stays untouched:

dir="$(mktemp -d ~/.cache/publish.XXXXXX)"
git archive vX.Y.Z | tar -x -C "$dir"
cd "$dir"                                              # then the backend directory, if any
uv version --frozen X.Y.Z
uv build --out-dir dist
uvx --isolated --from dist/*.whl <command> --version   # and --help of each area
UV_PUBLISH_TOKEN="$(cat <repo root>/.pypi/token)" uv publish dist/*

Then check the project's page as above and delete $dir. Token: only the repo's own .pypi/, never printed. None: stop, /repo:token; another repo's only with the user's yes. Say in the report that this upload has no build provenance (attest-build-provenance runs only on GitHub). pypi.yml stays: budget back, the next tag publishes with provenance; meanwhile a failed run per tag is the only cost.

9. Merge back, tidy

git merge --no-ff release/vX.Y.Z -m "Merge branch 'release/vX.Y.Z' into develop"   # from develop
git push origin develop
git worktree remove .claude/worktrees/release-vX.Y.Z
git branch -d release/vX.Y.Z && git push origin --delete release/vX.Y.Z

Report in the repo plugin's debrief format (output-styles/debrief.md); a failed health probe or smoke test is a Broken: line.

04 同仓库更多 Skills