heavy-duty/ceremony
7
0
Fork 2
Code Issues 1 Pull requests Projects Releases 8 Packages Wiki Activity Actions

docs: pin bumps update every ceremony reference; decide table is six rows

Browse source 
Round 1 (PR #48): codex-bot flagged the release-only bump described as a
one-line uses change while the same-tag rule two bullets up requires every
reference on one tag — a release-only setup has four (release caller +
three guards), so a one-line bump splits the consumer across versions.
The bump bullet and the pin-bump procedure now both require every ceremony
uses: reference updated together. Also the README called lib/decide.sh a
5-state table; the spec comment and rendered table have six rows.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
claude-bot-andresmgsl 2026-07-22 23:07:37 +00:00
parent 79261aa793
commit 55d0384c22
2 changed files with 17 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -98,7 +98,7 @@ and double-publish — and that job is the release's only chance to publish
The merge door runs on **every** push to main, and the `release` label
legitimately means two things (release ceremonies, and ordinary work *on*
the release machinery), so the door's first act is a decision: the 5-state
the release machinery), so the door's first act is a decision: the six-row
table in [lib/decide.sh](lib/decide.sh#L29-L61) (issue #8 — the comment
block *is* the spec, and the table is contract-tested offline). Rendered
for operators:

24
docs/CONSUMERS.md
View file

@ -297,13 +297,19 @@ Bumping the pin re-syncs the mirror in the same PR —
updates ([#1 D2](https://github.com/heavy-duty/ceremony/issues/1)).
Every `uses:` of this repo in the consumer — the two workflow callers
and the guard steps — names the same tag.
- **Bump by PR.** Before bumping, read the ceremony's own `CHANGELOG.md`
section for the new version (the release body on its
- **Bump by PR, every reference together.** Before bumping, read the
ceremony's own `CHANGELOG.md` section for the new version (the release
body on its
[releases page](https://github.com/heavy-duty/ceremony/releases) is
that section, verbatim). A repo that has adopted the agent team flow
bumps pin and mirror together —
[the pin-bump procedure](#the-pin-bump-procedure); a release-only repo's
bump is the one-line `uses:` change.
that section, verbatim). One bump PR updates **every** ceremony `uses:`
reference in the repo to the new tag — the workflow callers *and* each
guard step; a release-only setup already has four (the
[release caller](#release-workflow) plus the
[three CI guards](#bootstrap-a-new-repo)), and changing only one line
leaves the consumer split across ceremony versions, which the same-tag
rule above forbids. A repo that has adopted the agent team flow
additionally bumps the mirror in the same PR —
[the pin-bump procedure](#the-pin-bump-procedure).
- **One pin governs machinery and doctrine.** The ref in the consumer's
`release.yml` `uses:` line is the single pin: `docs-sync` reads it from
exactly there and verifies the `.ceremony/` mirror against it — there
@ -376,8 +382,10 @@ this is the checklist:
### The pin-bump procedure
Bumping the ceremony pin is **one PR carrying both halves**: the pin-line
change in the workflow callers, and the re-synced `.ceremony/` mirror —
Bumping the ceremony pin is **one PR carrying both halves**: every
ceremony `uses:` reference — the workflow callers *and* each guard step,
[all to the same new tag](#version-pinning) — and the re-synced
`.ceremony/` mirror —
run `docs-sync --fix` locally, or let the red `--check` on the bump PR
tell you what is stale. The CI guard is what makes a half-done bump —
pin without mirror, or mirror without pin — unmergeable (#19). This is