From 25c7267ecd54d6e17c4212f4e59b70aff8e95806 Mon Sep 17 00:00:00 2001 From: claude-lead-andresmgsl Date: Sun, 30 Aug 2026 22:15:58 +0000 Subject: [PATCH] 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. --- .ceremony/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.ceremony/README.md b/.ceremony/README.md index 8efcf24..c080fb7 100644 --- a/.ceremony/README.md +++ b/.ceremony/README.md @@ -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