Makes tagging a release prep the norm - #171
Merged
Merged
Conversation
The authority table, and the relay paragraph under it, kept the tag of a release with the operator however a consent arrived. The operator ruled on 2026-09-25 that the version bump and the tag of a release prep are the family norm, and that publishing is the operator's one release step. The table now gives the tag of a merged release prep a trigger of its own, the relay sentences drop tagging from what stays forbidden, and a Release preps paragraph records the ruling beside the other recorded exceptions. Merging, record flips and every other act the file reserves for the operator are unchanged. Documentation only: no code, no changelog fragment.
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.
What changed
The operator ruled on 2026-09-25 that the version bump and the tag of a release prep are the family norm, and that publishing is the operator's one release step. This file said a tag stays the operator's however a consent arrives. Now:
a release (tag, mix hex.publish, GitHub release) | never | alwaysis split in two. A newtagging a release preprow (trigger: the release bead's bump is merged toorigin/mainand the tag names that version at the merged commit), and the release row keepsmix hex.publishand the GitHub release with the operator, verdict unchanged.mix hex.publish, a GitHub release - stay forbidden" drops the tag, and "the version bump stays a release-bead bump with no tag and no publish" becomes no publish, with its tag the tag of that merged prep.CLAUDE.md: the version bump and the tag of a release prep are the family norm, not a grant a campaign consent has to name; once the prep is merged toorigin/main, the conductor (or the session that owns the release bead) tags that merged commit and pushes the tag; publishing is the operator's one release step, in every campaign; merging follows this file's merge row and nothing else the file reserves changes.Nothing else in the authority section moves: the merge row, record flips, a docs republish, and closing a mirrored bead read as before.
No changelog fragment:
changelog.d/README.mdexcludes documentation and agent tooling changes.Review
Gate: not run. Every file touched is outside the manifest's build paths and also-gated paths, so the commit row's docs-only clause applies.
Firewall and planning-id scans clean over the outbound diff, the commit message and this text.
Held for the operator's merge word; do not merge on green alone.