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

docs: record delivered 0.6.1 runner exercise
All checks were successful
CI / test (pull_request) Successful in 3m19s
Details
CI / release-exercise (pull_request) Successful in 13s
Details
CI / self-guards (pull_request) Successful in 9s
Details
CI / action-exercise (pull_request) Successful in 9s
Details
CI / docs-sync-exercise (pull_request) Successful in 9s
Details
Refs guard / refs-not-closing (pull_request) Successful in 9s
Details
labels / labels (pull_request) Successful in 11s
Details

Browse source
This commit is contained in:
Codex Review 2026-08-09 20:35:49 +00:00
parent 5693bee9f3
commit 2aafc04018
2 changed files with 22 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
changelog.d/217.md Normal file
View file

@ -0,0 +1,3 @@
### Changed
- `docs/RUNNER-PROBES.md` records the delivered 0.6.1 consumer exercise in the standing Forgejo runner venue (#217).

21
docs/RUNNER-PROBES.md
View file

@ -368,8 +368,25 @@ memory.
caller's `event.inputs` on this instance. Records:
[probe issues #4 and #5](https://forgejo.heavyduty.builders/heavy-duty/ceremony-runner-probe/issues/4)
(runs 6 and 7).
- A 0.6.0 consumer exercise once ceremony#198 has merged. (#198 merged
2026-08-05; this probe remains open.)
- **ceremony#217** — DELIVERED (2026-08-09). The standing venue used the
published consumer callers without rewrites or bypasses:
`labels.yml@0.6.1` and `labels-sweep.yml@0.6.1`. Opening fixture issue #7
drove event caller
[run 23](https://forgejo.heavyduty.builders/heavy-duty/ceremony-runner-probe/actions/runs/23)
and its dispatched sweep
[run 24](https://forgejo.heavyduty.builders/heavy-duty/ceremony-runner-probe/actions/runs/24);
the sweep wrote `needs-triage` on that issue under the workflow token. A
separate manual sweep was green in
[run 25](https://forgejo.heavyduty.builders/heavy-duty/ceremony-runner-probe/actions/runs/25).
Observer
[run 30](https://forgejo.heavyduty.builders/heavy-duty/ceremony-runner-probe/actions/runs/30)
recorded the released tag SHA `338cf5f754f0e87feefe9231b47910fb236ab4d0`,
both caller runs and the resulting label set in
[probe issue #10](https://forgejo.heavyduty.builders/heavy-duty/ceremony-runner-probe/issues/10).
The event caller loaded its reusable workflow at `@0.6.1`; both sweep runs
completed the reusable workflow's internal `CEREMONY_SELF_REF` checkout at
the real `0.6.1` tag. There was no candidate SHA rewrite and no dogfood
bypass.
Two venue lessons from the first drills, kept where the next probe author will
look: