From 1132a3b0bbfcfc7e782f3f0cdcae9ba196415076 Mon Sep 17 00:00:00 2001 From: Simon Koudijs Date: Sat, 24 Oct 2026 20:54:57 +0000 Subject: [PATCH 1/2] docs: narrow the release gate to checking the regenerated changelog #441 and #443 now carry a BEGIN_COMMIT_OVERRIDE, as #428 does. #419 shipped in 0.53.0 under the names it had then, so its entry needs no override. What is left is to confirm that release-please used each override once it regenerates the release PR. Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/TODO.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/TODO.md b/docs/TODO.md index 6c4fda5f..6ec8480e 100644 --- a/docs/TODO.md +++ b/docs/TODO.md @@ -3,16 +3,13 @@ The open work, in one list. Each item is one or two lines with a code pointer or the design page that argues it. Ranked within each group, most urgent first. **Before the next release** marks what should land before the next tag is cut (the last release is v0.53.0). Checked against `main` at -`05799999` plus #443 on 2026-10-24. +`1bc97904` on 2026-10-24. ## Before the next release -- [ ] **Override the changelog entries of #441 and #419.** Like #428's (overridden), #441's squash - footer narrates moves between shapes that never shipped (`from`/`names`/`selector` into - `consumerNamespaces`, `branches` renamed `branchPatterns`), and #419's override still names - `FluxTrigger`, `ArgoCDTrigger` and `spec.applyTriggerRef`, which #438 renamed. Give each a - `BEGIN_COMMIT_OVERRIDE` block that describes what ships, consistent with - [UPGRADING.md](UPGRADING.md), before the release PR is cut. +- [ ] **Check the release PR's changelog once it is regenerated.** #428, #441 and #443 carry a + `BEGIN_COMMIT_OVERRIDE` describing what ships; confirm release-please used each one, and that #442 + and #443 are listed. (#419 shipped in 0.53.0 under its own names, so its entry stays as released.) ## Applier claims and bi-directional editing From 7845f59f27914778691649592c50ce5804a4e0e9 Mon Sep 17 00:00:00 2001 From: Simon Koudijs Date: Sat, 24 Oct 2026 20:58:00 +0000 Subject: [PATCH 2/2] docs: close the release gate now that the changelog is checked #442 and #443 were dropped from the release PR: each PR description mentioned BEGIN_COMMIT_OVERRIDE in prose, and release-please took the text after it as the commit message, which does not parse. Both now carry a real override, and the regenerated release PR lists every commit with the wording that ships. Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/TODO.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/TODO.md b/docs/TODO.md index 6ec8480e..765141dc 100644 --- a/docs/TODO.md +++ b/docs/TODO.md @@ -7,9 +7,7 @@ should land before the next tag is cut (the last release is v0.53.0). Checked ag ## Before the next release -- [ ] **Check the release PR's changelog once it is regenerated.** #428, #441 and #443 carry a - `BEGIN_COMMIT_OVERRIDE` describing what ships; confirm release-please used each one, and that #442 - and #443 are listed. (#419 shipped in 0.53.0 under its own names, so its entry stays as released.) +Nothing open. The 0.54.0 release PR's changelog was checked against what ships on 2026-10-24. ## Applier claims and bi-directional editing