From a1e31e9c0a538a87c1789d8c013572bf044cc9a2 Mon Sep 17 00:00:00 2001 From: sudolulo Date: Mon, 13 Jul 2026 18:30:59 +0000 Subject: [PATCH] CHANGELOG: the barrier does not check the candidate's CI run That gate was removed as redundant -- the release job re-runs the full suite against the tagged commit, and release_gate proves a candidate points at it. The notes described a check that does not exist. --- CHANGELOG.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3b41301..2f480cc 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -12,10 +12,11 @@ worse than no alert, because one day it carries a security fix. - **`release.sh` — a two-stage release process, and a barrier that enforces it.** A stable `vX.Y.Z` tag is now only publishable if a `vX.Y.Z-rcN` tag points at the - **same commit** and that candidate's CI run passed. Candidates are invisible to - users — `update.sh` and the update alert both take the newest plain `vX.Y.Z` tag — - so debugging happens across rc1, rc2, rc3 at nobody's expense, instead of across - v0.5.0, v0.5.1, v0.5.2 at everybody's. + **same commit**, and the release job re-runs the entire suite against that tagged + commit before publishing. Candidates are invisible to users — `update.sh` and the + update alert both take the newest plain `vX.Y.Z` tag — so debugging happens across + rc1, rc2, rc3 at nobody's expense, instead of across v0.5.0, v0.5.1, v0.5.2 at + everybody's. bash release.sh 0.6.0 --rc # candidate. Invisible to users. bash release.sh 0.6.0 --promote # stable. Refused unless an rc passed HERE.