← ClaudeAtlas

releaselisted

Cut an AgentHub release using the repository's preflight, versioning, changelog, tagging, and post-release verification procedure. Use when preparing or publishing a release.
dinstein/agent-hub · ★ 3 · AI & Automation · score 76
Install: claude install-skill dinstein/agent-hub
# Releasing One tag push does the work. Everything before it is local and reversible; everything after it is public within seconds, so the cheap checks come first. --- ## 0. Preflight ```bash git fetch origin git status --short # must print nothing git log --oneline -1 origin/main # must equal local main git worktree list # anything here is NOT being released ``` **A release ships `main` exactly as it stands.** Nothing is cherry-picked. If a worktree holds work that belongs in this version, land it first by the [new-feature skill](../new-feature/SKILL.md) step 5 and start over at step 0. Otherwise say out loud which branches are being left out, so "I thought that was in" is caught now rather than by a user. ## 1. Choose the number Against the **user-visible surface**, not the size of the diff. When two rows could apply, take the lower one. | What changed | Bump | |---|---| | Docs, comments, tests, internal refactors; help text corrections | patch — `0.13.0` → `0.13.1` | | A new command or flag, a new capability, a changed default | minor — `0.13.1` → `0.14.0` | | A removed command or flag, or a moved frozen identifier ([docs/conventions.md#frozen-identifiers](../../../docs/conventions.md#frozen-identifiers)) | major | A pre-release carries a `-` (`0.14.0-rc1`) and the workflow marks the Release accordingly. ## 2. Bump VERSION ```bash new=0.13.2 printf '%s\n' "$new" > VERSION git diff --stat #