Skip to content

Makes tagging a release prep the norm - #235

Merged
johnnyt merged 1 commit into
mainfrom
docs/release-prep-tag-norm
Sep 26, 2026
Merged

johnnyt merged 1 commit into
mainfrom
docs/release-prep-tag-norm

Conversation

@johnnyt

@johnnyt johnnyt commented Sep 26, 2026

Copy link
Copy Markdown
Member

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:

  • Release-prep row: its last cell's "Tagging is not the agent's at all - the tag is the operator's, alongside the push and the publish" becomes "The tag of that prep, once it is merged to origin/main, is the agent's too; the publish stays the operator's". The bold mix hex.publish row 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.
  • Relay paragraph: "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".
  • Skills table: the /wurk:release line reads "the tag and the human-gated publish stay separate" (the skill still never tags).
  • A new Release preps paragraph, placed after the other recorded exceptions and word for word the same in every family package's 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 to origin/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.md excludes 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.

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

codecov Bot commented Sep 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@johnnyt
johnnyt merged commit c96f424 into main Sep 26, 2026
2 checks passed
@johnnyt
johnnyt deleted the docs/release-prep-tag-norm branch September 26, 2026 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant