From 7b00a1f0d244b05d6799eb863870761289c508ee Mon Sep 17 00:00:00 2001 From: Jer Miller Date: Mon, 7 Sep 2026 16:24:46 -0600 Subject: [PATCH] State the install-documentation rule rather than the cutover moment The closing paragraph described the pre-cutover state as present fact in a permanent document, and it goes false at the exact moment it describes, because the staged INSTALL.md and README.md edits land with that same first release publish. State the invariant instead. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_019K5mVVoGqXK2tBfXy5fSuw --- RELEASING.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index c20524b..4d8e114 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -299,9 +299,8 @@ require a new version. GitHub does not build, validate, approve, or define the release. There is no GitHub workflow or repository-setting gate. Skipping the mirror leaves a -complete, correct release. The install instructions move to the origin with the -first `release` publish; until that happens `INSTALL.md` and `README.md` still -name GitHub, and that is correct, because the `release` lane is empty. +complete, correct release. From the first `release` publish onward, the install +documentation names the origin. ## Host and advisory gates -- 2.51.2