History

clad2 935a813d75 fix(labels): wake the sweep over REST, so board events reconcile in seconds `.github/workflows/labels.yml` dispatched the sweep with `gh workflow run`, the eighth runtime gh call site the 0.6.0 merge reintroduced and the only one !204 did not port. On this forge the runner carries neither gh nor a GitHub API, so the step refused and the entire event-driven reconcile path ended there — every transition waiting up to an hour for the scheduled sweep. The workflow-dispatch endpoint has the SAME shape on both forges: POST {api}/repos/{owner}/{repo}/actions/workflows/{file}/dispatches {"ref": "<branch>", "inputs": {...}} -> 204, empty body so the step no longer decides a forge at all. The CEREMONY_FORGE_CLIENT=gh declaration and both inline refusals are removed rather than ported, and test/no-runtime-gh.test.sh now asserts their ABSENCE — an opt-out with no gh behind it is a standing permission slip. The ref is supplied explicitly and taken from the repository, never from GITHUB_REF_NAME: on a pull_request_target run that is `<n>/merge`, which is not a branch. A non-204 still fails the job, keeping the misconfiguration alarm the trigger exists to be, and the diagnostic explains Forgejo's empty 500 rather than passing a bare status to a reader who will go looking for an outage that is not there. test/labels-dispatch.test.sh extracts the shipped step and executes it against a recording stub, asserting the method, endpoint, ref and inputs actually sent. Dropping the inputs or ignoring a non-204 both red the suite. Refs #205		2026-08-05 16:58:05 +00:00
..
192.md	fix(forgejo): a read failure names its verb too, and the tests assert the whole diagnostic (#192 )	2026-08-05 13:11:33 +00:00
195.md	fix(labels): panel and triage name identities that exist on this forge (#195 )	2026-08-04 19:09:16 +00:00
198.md	fix(198): the action fails closed, the caller decides scheduling, the guard decides the forge (#198 )	2026-08-05 12:30:28 +00:00
200.md	fix(upstream-delta): discovery is git's index, not the filesystem (#200 )	2026-08-05 14:10:56 +00:00
201.md	fix(docs-sync): the mirror is fetched from the forge in play, never a built-in one (#201 )	2026-08-05 11:16:23 +00:00
205.md	fix(labels): wake the sweep over REST, so board events reconcile in seconds	2026-08-05 16:58:05 +00:00
209.md	fix(forge): forge_commit_at — Forgejo serves a single commit at /git/commits/{sha} (#209 )	2026-08-05 15:01:32 +00:00
210.md	test(issueflow): each of the three sites is caught by behaviour, not only by the pin (#210 )	2026-08-05 14:37:37 +00:00
README.md	feat: ceremony flips to grouped — changelog.d/shape = grouped, five fragments converted, docs per D6	2026-07-25 13:14:05 +00:00
shape	feat: ceremony flips to grouped — changelog.d/shape = grouped, five fragments converted, docs per D6	2026-07-25 13:14:05 +00:00

README.md

changelog.d/ — the next release's section, one fragment per issue

Machine-assembled by bin/changelog-assemble (#112): every PR that changes behavior writes one file here — <issue>.md, the exact prose that will be published, nothing else — and the release PR folds them all into the next ## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct filenames never conflict, which is this directory's whole reason to exist. This README is the marker that keeps the directory tracked when it holds no fragments (#112 D1) — changelog-armed refuses a tree without it; do not delete it. The shape sentinel beside it declares the set's shape — grouped here, so every fragment carries ### headings (#182).