History

claude-lead-andresmgsl 25c7267ecd All checks were successful ci / test (push) Successful in 14s Details docs: move the .ceremony/ pin record to 0.6.3 The mirror was re-vendored from ceremony 0.6.3; this file still named 0.6.1 as the pin in both places.		2026-08-30 22:15:58 +00:00
..
AGENTS.md	docs: re-vendor .ceremony/ from ceremony 0.6.3	2026-08-30 22:15:44 +00:00
BUILDER.md	docs: re-vendor .ceremony/ from ceremony 0.6.3	2026-08-30 22:15:45 +00:00
LABELS.md	docs: re-vendor .ceremony/ from ceremony 0.6.3	2026-08-30 22:15:46 +00:00
README.md	docs: move the .ceremony/ pin record to 0.6.3	2026-08-30 22:15:58 +00:00
RELEASES.md	docs: re-vendor .ceremony/ from ceremony 0.6.3	2026-08-30 22:15:47 +00:00
REVIEWER.md	docs: re-vendor .ceremony/ from ceremony 0.6.3	2026-08-30 22:15:49 +00:00
TRIAGE.md	docs: re-vendor .ceremony/ from ceremony 0.6.3	2026-08-30 22:15:50 +00:00

README.md

.ceremony/ — the vendored doctrine mirror

Never edit these files ad hoc. The six manifest-listed doctrine files are byte-identical copies of heavy-duty/ceremony at 0.6.3, but stoke does not run docs-sync or re-diff the mirror in CI. Change doctrine upstream through its own flow, then re-vendor it here when the pin moves.

The labels doctrine is vendored manually from heavy-duty/ceremony at 0.6.3 because stoke keeps its own tag-driven .forgejo/workflows/release.yml. docs-sync --fix cannot run until or unless a future issue adopts the ceremony release-workflow pin; until then, doctrine updates must re-vendor the pinned manifest manually.