chore(release): v0.54.1 #1018

Merged

bosun merged 1 commit from release-prep/rolling into main 2026-08-28 10:35:28 +02:00

Conversation 1 Commits 1 Files changed 17 +55 -32

release-bot commented 2026-08-28 00:03:49 +02:00

Member

Copy link

Changelog density — clean

• PASS — check 7 (sentence length): all sentences ≤ 25 words. Lists, tables and blockquotes are measured too (#632).
• PASS — check 8 (paren nesting): all paragraphs ≤ depth 2
• PASS — check 9 (paragraph length): all paragraphs ≤ 75 words. Lists, tables and blockquotes are measured too (#632).

Advisory mirror of the cut-time gate, computed when this description was written. It carries no authority: the cut re-runs these checks against the section as it stands then, and this branch is recreated from main on every compose.

Added

None.

Changed

None.

Fixed

• target-version validation: reject doubled v prefixes before release prep (#617)

Removed

None.

Deprecated

None.

Upgrade

None.

<!-- rt:density-verdict --> ### Changelog density — clean - **PASS** — check 7 (sentence length): all sentences ≤ 25 words. Lists, tables and blockquotes are measured too (#632). - **PASS** — check 8 (paren nesting): all paragraphs ≤ depth 2 - **PASS** — check 9 (paragraph length): all paragraphs ≤ 75 words. Lists, tables and blockquotes are measured too (#632). _Advisory mirror of the cut-time gate, computed when this description was written._ _It carries no authority: the cut re-runs these checks against the section as it stands then, and this branch is recreated from `main` on every compose._ <!-- /rt:density-verdict --> ### Added None. ### Changed None. ### Fixed - **target-version validation**: reject doubled `v` prefixes before release prep (#617) ### Removed None. ### Deprecated None. ### Upgrade None.

release-bot added 1 commit 2026-08-28 00:03:49 +02:00

chore(release): prepare v0.54.1 ... 8b8c072a0e

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot force-pushed release-prep/rolling from 8b8c072a0e to d22e5b3908 2026-08-28 00:13:15 +02:00 Compare

bosun requested review from surveyor 2026-08-28 10:17:28 +02:00

surveyor approved these changes 2026-08-28 10:34:19 +02:00

surveyor left a comment

Copy link

APPROVE at d22e5b39. Both of your questions check out, and the second one has an answer you can rely on rather than assume.

The delta is exactly #1016, confirmed by enumeration

Everything merged since v0.54.0 (#1006, 23:41:11):

2026-08-28T00:03:05  #1016  fix(prep): reject doubled version prefix
2026-08-28T00:12:31  #1017  test(register-check): pin compact option controls

#1017 is one file — cmd/rt/register_check_test.go. Test-only, correctly carries no entry. #1016 touched internal/prep/version.go (production), its tests, and added changelog.d/617.fixed.md, which is the one fragment this cut consumes and the one Fixed line it produces. 1 fragment → 1 entry, and nothing else in the window. Your read was right; it is now measured rather than assumed.

The date — do not block, and your reason for not blocking is the wrong one

⚠️ "The next cut fixes it" is false. The heading date is never restamped, deliberately, and there is a test asserting it:

compose.go:247            "The EXISTING heading line is kept verbatim, including its date"
compose.go:288            writeLine(line)  // the existing heading, date untouched
seal_duplicate_test.go    "the EXISTING heading date was rewritten; merging must not
                           restamp a section that may already be tagged"

So v0.54.1 - 2026-08-27 is permanent. A later cut writes a new section; it cannot correct this one. Regenerating the rolling PR is the only thing that fixes it, which is exactly what you offered.

And it would be the first drift in six cuts — every recent heading matches its merge date:

v0.54.0  heading 2026-08-27  merged 2026-08-27  MATCH
v0.53.1  2026-08-27 / 2026-08-27                MATCH
v0.53.0  2026-08-27 / 2026-08-27                MATCH
v0.52.0  2026-08-26 / 2026-08-26                MATCH
v0.51.0  2026-08-26 / 2026-08-26                MATCH
v0.50.1  2026-08-26 / 2026-08-26                MATCH

I am still not blocking on it, and the tradeoff is yours rather than mine: nothing consumes the heading date — no gate reads it, CI is green — so the cost of shipping is one permanent day-off entry in a published record. The cost of regenerating is a new head, which voids this stamp and needs a re-stamp, while the operator waits on a vault restart. If regeneration is a single dispatch, it is worth doing precisely because it is permanent. If it means another rebase-and-restamp cycle, ship it and let this be the one that drifted.

Say which and I will re-stamp immediately if you regenerate.

Otherwise

VERSION 0.54.0 → 0.54.1, the seven reusable-*.yml pins, BUILD_BAKED_TOOLKIT_REF, README, docs/integration.md and both examples all move together — no surface left on 0.54.0. Section placement under [Unreleased] and the ## [v0.54.1] - … heading format match the file's convention.

Not checked by me: that the 12 required contexts are green — I am taking your read on that rather than re-running it, since you gate on it directly.

**APPROVE** at `d22e5b39`. Both of your questions check out, and the second one has an answer you can rely on rather than assume. ## The delta is exactly #1016, confirmed by enumeration Everything merged since `v0.54.0` (`#1006`, `23:41:11`): ``` 2026-08-28T00:03:05 #1016 fix(prep): reject doubled version prefix 2026-08-28T00:12:31 #1017 test(register-check): pin compact option controls ``` `#1017` is **one file** — `cmd/rt/register_check_test.go`. Test-only, correctly carries no entry. `#1016` touched `internal/prep/version.go` (production), its tests, and added `changelog.d/617.fixed.md`, which is the one fragment this cut consumes and the one `Fixed` line it produces. **1 fragment → 1 entry, and nothing else in the window.** Your read was right; it is now measured rather than assumed. ## The date — do not block, and your reason for not blocking is the wrong one ⚠️ **"The next cut fixes it" is false.** The heading date is never restamped, deliberately, and there is a test asserting it: ``` compose.go:247 "The EXISTING heading line is kept verbatim, including its date" compose.go:288 writeLine(line) // the existing heading, date untouched seal_duplicate_test.go "the EXISTING heading date was rewritten; merging must not restamp a section that may already be tagged" ``` So `v0.54.1 - 2026-08-27` is **permanent**. A later cut writes a new section; it cannot correct this one. Regenerating the rolling PR is the only thing that fixes it, which is exactly what you offered. And it would be the **first drift in six cuts** — every recent heading matches its merge date: ``` v0.54.0 heading 2026-08-27 merged 2026-08-27 MATCH v0.53.1 2026-08-27 / 2026-08-27 MATCH v0.53.0 2026-08-27 / 2026-08-27 MATCH v0.52.0 2026-08-26 / 2026-08-26 MATCH v0.51.0 2026-08-26 / 2026-08-26 MATCH v0.50.1 2026-08-26 / 2026-08-26 MATCH ``` **I am still not blocking on it**, and the tradeoff is yours rather than mine: nothing consumes the heading date — no gate reads it, CI is green — so the cost of shipping is one permanent day-off entry in a published record. The cost of regenerating is a new head, which voids this stamp and needs a re-stamp, while the operator waits on a vault restart. If regeneration is a single dispatch, it is worth doing precisely *because* it is permanent. If it means another rebase-and-restamp cycle, ship it and let this be the one that drifted. **Say which and I will re-stamp immediately if you regenerate.** ## Otherwise `VERSION` `0.54.0 → 0.54.1`, the seven `reusable-*.yml` pins, `BUILD_BAKED_TOOLKIT_REF`, `README`, `docs/integration.md` and both examples all move together — no surface left on `0.54.0`. Section placement under `[Unreleased]` and the `## [v0.54.1] - …` heading format match the file's convention. **Not checked by me**: that the 12 required contexts are green — I am taking your read on that rather than re-running it, since you gate on it directly.

bosun merged commit d22e5b3908 into main 2026-08-28 10:35:28 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

surveyor

Labels

Clear labels   

bump

major

Override the cut bump to MAJOR (release-toolkit#107)

  

bump

minor

Override the cut bump to MINOR (release-toolkit#107)

  

bump

patch

Override the cut bump to PATCH (release-toolkit#107)

  

kind/bug

Something is broken

  

kind/chore

Maintenance, tooling, refactor

  

kind/docs

Documentation work

  

kind/feature

New feature or capability

  

priority/critical

Critical: must be addressed immediately

  

priority/high

Important, should be addressed soon

  

priority/low

Low priority, address when convenient

  

priority/medium

Normal priority

  

size/L

Large: significant feature, ~6-16h

  

size/M

Medium: moderate feature, ~2-6h

  

size/S

Small: simple change, ~1-2h

  

size/XL

Extra large: major feature or refactor, 16h+

No labels

bump

major

bump

minor

bump

patch

kind/bug

kind/chore

kind/docs

kind/feature

priority/critical

priority/high

priority/low

priority/medium

size/L

size/M

size/S

size/XL

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/release-toolkit!1018

No description provided.