claude-bot-andresmgsl/ceremony
1
0
Fork 0
forked from heavy-duty/ceremony
Code Pull requests Activity

docs: CONSUMERS release-state notes say 0.2.0 shipped the issues: block (#137 D6)

Browse source 
The three sites called ceremony#32 machinery unreleased after 0.2.0
(tagged 2026-07-24) became the first tag carrying it: the in-stub comment
above the issues: block, the issues: adoption paragraph, and the
triage-actors= paragraph. All three now state availability at 0.2.0 and
later; the 0.1.0-omission guidance and the parse-failure sentence stay —
still true. No type list moves (the caller/stub issues: subset drift is
#144, not this PR).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
claude-bot-andresmgsl 2026-07-24 13:13:31 +00:00
parent c0e796b6c9
commit 48a3052934
1 changed files with 11 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/CONSUMERS.md
View file

@ -288,7 +288,8 @@ on:
# add them with the pin bump to the first tag carrying ceremony#137. They
# wake the sweep that clears blocker:unrequested when the panel is asked.
types: [opened, reopened, ready_for_review, converted_to_draft, synchronize, labeled, unlabeled, review_requested, review_request_removed]
# Unreleased — not in 0.1.0; add only with the first tag carrying ceremony#32.
# Available at 0.2.0 and later (the first tag carrying ceremony#32); a
# consumer pinned to 0.1.0 omits this block.
issues:
types: [opened, labeled, unlabeled, assigned, unassigned, closed]
permissions:
@ -307,9 +308,10 @@ repositories allow check data to be read regardless, but a private consumer
needs both explicit reads above; without them the failure appears as an empty
`state:*` axis on the board rather than a red workflow run.
The `issues:` trigger is **unreleased** and is not in `0.1.0`. A consumer
pinned to `0.1.0` omits it. Add it only when bumping every ceremony reference
to the first tag carrying ceremony#32; never mix refs to adopt it early.
The `issues:` trigger is available at `0.2.0` and later — `0.2.0` is the
first tag carrying ceremony#32. A consumer pinned to `0.1.0` omits it. Adopt
it only by bumping every ceremony reference to `0.2.0` or later; never mix
refs to adopt it early.
`pull_request_target` is intentional: fork PRs need the base repository's
token to write labels. The reusable workflow executes no PR code. It checks
@ -332,11 +334,11 @@ scope:cli|C5DEF5|The command-line surface
scope:docs|C5DEF5|Documentation
```
The mandatory `triage-actors=` setting is also **unreleased** and is not
accepted by `0.1.0`. At that tag the file contains `panel=` plus scope rows
only; adding `triage-actors=` is a parse failure, not an ignored setting. Add
it at the same pin bump as the `issues:` trigger, to the first tag carrying
ceremony#32 — never before it and never through mixed refs.
The mandatory `triage-actors=` setting is likewise accepted at `0.2.0` and
later, and not by `0.1.0`. At that tag the file contains `panel=` plus scope
rows only; adding `triage-actors=` is a parse failure, not an ignored setting.
Add it at the same pin bump as the `issues:` trigger — `0.2.0` or later —
never before it and never through mixed refs.
Both actor lists are whitespace-separated. `triage-actors` names the identities
allowed to mint issues without the sweep applying `needs-triage`. Label rows use exactly