Repository navigation
Makes tagging a release prep the norm - #235
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.
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
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 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:
origin/main, is the agent's too; the publish stays the operator's". The boldmix hex.publishrow is untouched. ADR-0006 keeps publishing non-delegable and places tagging among the release mechanics that have a trigger, so this is consistent with it.mix hex.publish, and tagging or cutting a release stay forbidden" drops tagging; the release-prep opening now includes the tag of the merged prep. The 2026-09-02 recorded exception's "the tag, the push and the publish stay the operator's" becomes "the publish stays the operator's, and the tag follows the Release preps paragraph below"./wurk:releaseline reads "the tag and the human-gated publish stay separate" (the skill still never tags).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.