Repository navigation
docs(release): point to the release files; rc first, rerun, never move a tag - #56
Conversation
kaibo review (cast
|
Why: Amy: "let's make sure it's documented in README.md and (briefly) AGENTS.md". The v0.6.0 release needed three attempts and steps that were not documented. Approach: README "Releases" now has the procedure (CHANGELOG, rc tag, check, final tag on the same commit, check), recovery for a 401 from the tap and a ghcr permission_denied, the tap token command that tests before it stores, and the sha256-* install box note. AGENTS.md has short steps and two hazards. Learned: kaibo review: an rc run still needs the secret (the preflight checks it), release.yml runs no tests, and `gh release view` has no isLatest field. Next: The next release follows this text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 🤖 Reviewed by DeepSeek (deepseek-flash) via kaibo
Why: Amy: "should replace 'Amy' with @tobert or 'maintainers'". Approach: AGENTS.md already says "Ask a maintainer"; use the same term. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Why: Amy: "you added way too much to the README.md, just say where the process is, say a lot less, we can infer most of it and just need pointers". Approach: README points to release.yml and .goreleaser.yml, whose comments explain each step, and lists four rules the code does not show. The token scope is in release.yml:62-64 and .goreleaser.yml:133-134. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Why: Amy: "we'll get a 0.6.2 rolling to do an e2e". We agreed on 0.6.1, because 0.6.0 is the last release. Approach: Two terse bullets. The actions bumps (#55) and the docs (#56) do not change what users get. Next: Tag v0.6.1-rc.1, then v0.6.1 on the same commit to test #54. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Shortens README.md "Releases" to a pointer to release.yml and .goreleaser.yml, whose comments explain each step. It adds four rules that the code does not show:
v0.X.Y-rc.1first. An rc does not update the Homebrew tap orlatest.HOMEBREW_TAP_GITHUB_TOKEN.gh run rerun.AGENTS.md "Releases" now has an rc step before the final tag on the same commit. It also says that only a maintainer can set the tap token.
The v0.6.0 release taught these rules. GoReleaser now gets the pushed tag (#54), so an rc and the final tag can share a commit.
An earlier draft documented the full procedure in README.md. A kaibo review comment on this PR covers that draft. The draft was too long; the files the README points to already explain those steps.
🤖 Generated with Claude Code