heavy-duty/stoke
7
1
Fork 1
Code Issues 1 Pull requests Projects Releases 3 Packages Wiki Activity Actions

docs: move the .ceremony/ pin record to 0.6.3
All checks were successful
ci / test (push) Successful in 14s
Details

Browse source 
The mirror was re-vendored from ceremony 0.6.3; this file still named 0.6.1 as
the pin in both places.
This commit is contained in:
claude-lead-andresmgsl 2026-08-30 22:15:58 +00:00
parent 5ec01f56b7
commit 25c7267ecd
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.ceremony/README.md
View file

@ -2,11 +2,11 @@
Never edit these files ad hoc. The six manifest-listed doctrine files are
byte-identical copies of
[heavy-duty/ceremony](https://github.com/heavy-duty/ceremony) at 0.6.1, but
[heavy-duty/ceremony](https://github.com/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.1
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