Repository navigation
Release guide: the merged prep's tag is the conductor's - #237
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
The release extension still said the tag and its push stayed with the operator, in the section on mix hex.publish and again under the release trigger. CLAUDE.md's release-prep row and its Release preps paragraph now give the tag of a merged release prep to the conductor or the session that owns the release bead. Both sentences now say that, in this file's own words, and the publish (mix hex.publish, a docs republish included) stays the operator's one release step. Agent tooling only: no code, and no changelog fragment (changelog.d/README.md excludes agent tooling changes). Refs: px-fgiq
johnnyt
force-pushed
the
px-fgiq-release-tag-wording
branch
from
September 27, 2026 15:31
8335bcd to
1c6340c
Compare
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 release extension (
.claude/wurk/release.md) carried two sentences that kept the tag with the operator: "Tag and push stay separately human-gated." under themix hex.publishsection, and "The tag, the push and the publish stay the operator's" under the release trigger. CLAUDE.md now says otherwise: the release-prep mechanics row gives the tag of a merged prep to the agent ("The tag of that prep, once it is merged toorigin/main, is the agent's too"), and the Release preps paragraph names who ("the conductor or the session that owns the release bead tags that merged commit with the new version and pushes the tag"). The first sentence now points at the release trigger as the tag's owner; the second restates the Release preps paragraph and keeps the publish -mix hex.publish, a docs republish included - as the operator's one release step that no consent or relay delegates..claude/wurk/commit.mdwas read and says nothing about the tag, so it is unchanged.Review (in-turn, docs-only): each new sentence was checked against CLAUDE.md's
mix hex.publishrow, the release-prep row and the Release preps paragraph. Both grant nothing CLAUDE.md does not, and no authority row or other file changes. No gate run:.claude/is outside the manifest's gated paths, and CLAUDE.md's commit row lets a change touching no Elixir code commit on review of the diff alone. No changelog fragment:changelog.d/README.mdexcludes agent tooling changes.Provenance: ADR-0006 still describes tag, push and publish as the human's steps at release. It is a record and is left alone here; the wording change was ruled by the operator, 2026-09-25, and recorded in CLAUDE.md.