Release and commit guides: the merged prep's tag is the conductor's - #350
Merged
Merged
Conversation
release.md and commit.md still described the tag of a release prep as the operator's. CLAUDE.md now carries a separate tag row and a Release preps paragraph: once the version bump is merged to origin/main, the conductor or the session that owns the release bead tags that merged commit with the new version. Both guides now say so in their own words, and both keep the publish (mix hex.publish) as the operator's. release.md also named the 2.4.0 prep as the most recent release prep; it now names the 2.9.0 prep, f2365bb, which is tagged v2.9.0, touched exactly the four files the table lists, moved the README pin from ~> 2.8 to ~> 2.9, and kept the version reasoning in its commit body. Docs only: no path in the gate's build_paths changes, and agent tooling takes no changelog fragment. Refs: st-tnov, st-48z7
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
1 participant
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.
Summary
.claude/wurk/release.mdand.claude/wurk/commit.mdstill said the tag of a release prep belongs to the operator. This changes those sentences, and only those, plus the stale reference-prep sha inrelease.md. Two files change; nothing else.release.md, "What a release here still is not": the lead sentence now says the tag comes after the merge and the publish never comes from an agent; the old bullet that folded the tag into "a release" is split into the tag row and the publish row, each quoted fromCLAUDE.md; the closing sentence that said "the tagging is the operator's" now says the conductor or the session that owns the release bead tags the merged commit and pushes the tag, and the publish (mix hex.publish, a docs republish included) stays the operator's.commit.md, "Version bump: release-prep commits only": "the tag and publish that follow are always the user's" becomes: once the prep is merged toorigin/main, the conductor or the session that owns the release bead tags the merged commit; the publish (mix hex.publish) is always the user's.release.mdnamede739263(the 2.4.0 prep) as the most recent release prep and the model for every step. It now namesf2365bb, the 2.9.0 prep. Each claim the file makes about the reference was re-checked againstf2365bb: tagv2.9.0points at it; it touched exactlymix.exs,README.md,CHANGELOG.mdand deletedchangelog.d/fragments; it moved the README pin from~> 2.8to~> 2.9; itsCHANGELOG.mdheading has no dash; its commit body carries the version reasoning.Review
Every new sentence was read against
CLAUDE.md's authority table rows "tagging a release prep" and "a release (mix hex.publish, GitHub release)" and its Release preps paragraph. The two row quotes inrelease.mdare verbatim; the prose restates the paragraph (tag after the merge toorigin/main, by the conductor or the owning session, the tag naming the new version at the merged commit) and grants nothing it does not. Every sentence about the publish still assigns it to the operator.CLAUDE.mditself is unchanged. Both files were searched for any other sentence assigning the tag to the operator or the user, or saying a prep carries no tag; none remained beyond the ones changed here.Gate
No path under the gate's
build_pathschanges (.claude/is outside them), andCLAUDE.md's commit row lets a change touching no Elixir code commit on review of the diff alone, so the quality gate did not run. No changelog fragment:changelog.d/README.mdexcludes agent tooling changes.