Repository navigation
Release guide: the merged prep's tag is the conductor's - #38
Merged
Merged
Conversation
The closing section of .claude/wurk/release.md still kept the tag of a release prep with the operator and said a prep lands only under a consent clause that names it. CLAUDE.md's tag row and its Release preps paragraph say otherwise: a prep on a release bead the operator has named is the family norm, and once it is merged to origin/main the conductor or the session that owns the release bead tags that merged commit and pushes the tag. The section now says so in the file's own words. Publishing (mix hex.publish, a docs republish included) and the release itself stay the operator's. Documentation only: no code, no changelog fragment (changelog.d/README.md excludes agent tooling changes). Refs: sd-84v
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.
The closing section of
.claude/wurk/release.md("What a release here still is not") said the tag of a release prep was the operator's and that a prep request carried no tag and landed only under a consent clause naming it. That paragraph is rewritten, and it is the only change. It now says whatCLAUDE.mdalready says, in the release guide's own voice: a release prep on a release bead the operator has named is the family norm and lands through the ordinary commit, push and request rows; once it is merged toorigin/main, the conductor or the session that owns the release bead tags that merged commit with the new version and pushes the tag, never before; publishing (mix hex.publish, a docs republish included) and the release itself stay the operator's, and no consent or relay delegates them.Review (in-turn, docs-only): each sentence was checked against
CLAUDE.md's authority table row "a release prep (a version bump and a changelog promotion) and its tag" and the "Release preps." paragraph under it; nothing is granted that those do not grant, and no sentence about the publish moves to an agent. The rest ofrelease.mdwas re-read for any other sentence keeping the tag with the operator and none remains..claude/wurk/commit.mddoes not exist in this repo, so there was nothing to change there..claude/is in neithergate.build_pathsnorgate.also_gated_paths, so underCLAUDE.md's commit row this change has no gate to run; no changelog fragment, becausechangelog.d/README.mdexcludes agent tooling changes.