ceremony/.github/workflows
cluade-reviewer-andresmgsl 9a229ee643
Some checks failed
CI / test (pull_request) Successful in 1m25s
CI / release-exercise (pull_request) Successful in 9s
CI / self-guards (pull_request) Failing after 5s
CI / action-exercise (pull_request) Successful in 4s
CI / docs-sync-exercise (pull_request) Successful in 4s
labels / labels (pull_request) Successful in 1m15s
release: stamp 0.4.1
The three stamps, in one commit as the ceremony requires: VERSION goes
bare, the self-ref pin follows it, and the changelog section is the
assembler's output rather than a hand edit.

0.4.1 is the forge release. Everything in the section comes from #188's
single fragment: ceremony stops being gh-only. `lib/forge.sh` selects a
backend from the runner's own environment, `lib/forge-github.sh` and
`lib/forge-forgejo.sh` implement one call surface twice, and the
reconcilers preflight before they sweep — so a GitHub-shaped client
pointed at a Forgejo instance is a named refusal instead of a sweep that
reads nothing and reports success.

Verified on this instance before stamping: the first post-merge `labels`
run on main (7fc9afe, task 467) came back SUCCESS — the reconciler's
first green run on Forgejo, and the evidence the section's claims are
not merely asserted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-04 10:01:21 +00:00
..
ci.yml feat(forge): timeline normalizer, portable PR activity, shellcheck install (#188) 2026-08-03 15:13:30 +00:00
labels.yml release: stamp 0.4.1 2026-08-04 10:01:21 +00:00
release-exercise.yml test: exercise release fixtures fragment-shaped; record the #115/#116 trio interaction 2026-07-24 11:11:23 +00:00
release.yml release: stamp 0.4.1 2026-08-04 10:01:21 +00:00
self-labels.yml docs: correct labels maintenance cadence 2026-07-29 10:37:03 +00:00
self-release.yml feat: dogfood bootstrap — ceremony adopts its own ceremony (#11) 2026-07-22 22:19:50 +00:00