Repository navigation
docs(release-agent): codefly publish cuts the release, never a hand tag - #189
Merged
antoinetoussaint-byte merged 1 commit intoOct 27, 2026
Merged
Conversation
The skill told the next agent to `git tag -a v0.0.N && git push origin v0.0.N` after merging a hand-written version bump. That contradicts how this repo is actually released — main's history is a series of `release: v0.0.N` pull requests — and it contradicts the rule that publish owns the release: a hand tag skips the pre-flight gates, the release-grade agent CI and the asset upload, which is how a release once shipped from a commit whose CI had never run. The walk is now `codefly publish patch` from a clean, up-to-date main clone, with what publish does end to end, what its pre-flight refuses, and the two traps worth knowing: re-run it to finish a merged-but-untagged release rather than bumping again, and never start a second publish while one is waiting. Pinning core stays a PR of its own, because the version bump is publish's to write. The version/tag/archive contract and the CGO section are unchanged; they were already right. Written while releasing v0.0.168 by that path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
antoinetoussaint-byte
requested a review
from AntoineToussaint
as a code owner
October 27, 2026 16:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
A fix to the procedure this repo hands the next agent.
release-agenttold it to cut thetag by hand:
That contradicts how this repo is actually released — main's history is a series of
release: v0.0.Npull requests — and it contradictscodefly publishowning the release. Ahand tag skips the pre-flight gates, the release-grade agent CI, and the asset upload and
install-URL verification. That is how a release once shipped from a commit whose CI had never
run.
What changed
codefly publish patchfrom a clean, up-to-datemainclone, with whatpublish does end to end (bump → release PR → release-grade agent CI → tag → GitHub release
with loader archives and SBOMs) and what its pre-flight refuses (dirty tree, not on main,
behind origin, tag already exists).
publishtofinish a merged-but-untagged release rather than bumping again, and never start a second
publishwhile one is waiting, or the re-run opens the NEXT bump instead of tagging the oneon main.
Unchanged, because they were already right: the three-item version/tag/archive contract with
core's downloader, and why the release build needs CGO and the cross toolchain.
Written while cutting v0.0.168 and v0.0.169 by that path, which is where the gaps showed.
🤖 Generated with Claude Code