chore(release): v0.54.0 #1006

Merged

bosun merged 1 commit from release-prep/rolling into main 2026-08-27 23:41:11 +02:00

Conversation 1 Commits 1 Files changed 27 +63 -85

release-bot commented 2026-08-27 12:41:19 +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

• A cut refuses while a previous release is an unpublished draft: the block is named on the PR (#811).

Changed

• fragment coverage: PRs now declare a changelog fragment or an explicit reason when no entry is needed (#498).
• branch strategy: clarify current main-line guidance and preserve superseded history (#604)
• Forgejo client comments: distinguish the retired shell source from the live Go contract (#990)

Fixed

• A wrapped Intended-targets: trailer: the refusal now names the anchoring problem instead of repeating itself (#1008).
• Changelog body gate: keep em-dash headers valid under byte locales (#611)
• changelog gates: fail mixed release sections and keep fragment brevity as guidance (#627)
• test fixtures: use unambiguous Git option spelling for commit helpers (#897)
• Push preflight: distinguish absent, hidden, unreadable, and failed branch-protection reads (#914)
• Forgejo client: document the deliberate dry-run release lookup exception (#957)
• AC-closure CI diagnostics: distinguish crashed fixtures from live fixtures that time out without publishing a port (#992)

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 - **A cut refuses while a previous release is an unpublished draft**: the block is named on the PR (`#811`). ### Changed - **fragment coverage**: PRs now declare a changelog fragment or an explicit reason when no entry is needed (#498). - **branch strategy**: clarify current main-line guidance and preserve superseded history (#604) - **Forgejo client comments**: distinguish the retired shell source from the live Go contract (#990) ### Fixed - **A wrapped `Intended-targets:` trailer**: the refusal now names the anchoring problem instead of repeating itself (`#1008`). - **Changelog body gate**: keep em-dash headers valid under byte locales (#611) - **changelog gates**: fail mixed release sections and keep fragment brevity as guidance (#627) - **test fixtures**: use unambiguous Git option spelling for commit helpers (#897) - **Push preflight**: distinguish absent, hidden, unreadable, and failed branch-protection reads (#914) - **Forgejo client**: document the deliberate dry-run release lookup exception (#957) - **AC-closure CI diagnostics**: distinguish crashed fixtures from live fixtures that time out without publishing a port (#992) ### Removed None. ### Deprecated None. ### Upgrade None.

release-bot added 1 commit 2026-08-27 12:41:19 +02:00

chore(release): prepare v0.54.0 ... 4fc1b0a580

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot force-pushed release-prep/rolling from 4fc1b0a580 to 0ed0936043 2026-08-27 12:46:47 +02:00 Compare

release-bot force-pushed release-prep/rolling from 0ed0936043 to 221250b30f 2026-08-27 13:00:09 +02:00 Compare

release-bot force-pushed release-prep/rolling from 221250b30f to 229fcaf09d 2026-08-27 13:04:56 +02:00 Compare

release-bot force-pushed release-prep/rolling from 229fcaf09d to 4dbe3b0150 2026-08-27 13:20:42 +02:00 Compare

release-bot force-pushed release-prep/rolling from 4dbe3b0150 to 2a0dbbcc4a 2026-08-27 13:33:23 +02:00 Compare

release-bot force-pushed release-prep/rolling from 2a0dbbcc4a to e2a8e02316 2026-08-27 17:17:03 +02:00 Compare

release-bot force-pushed release-prep/rolling from e2a8e02316 to 0394420fda 2026-08-27 17:22:43 +02:00 Compare

release-bot force-pushed release-prep/rolling from 0394420fda to c591e15432 2026-08-27 19:07:07 +02:00 Compare

release-bot force-pushed release-prep/rolling from c591e15432 to 1e0e14f0ce 2026-08-27 21:42:07 +02:00 Compare

release-bot force-pushed release-prep/rolling from 1e0e14f0ce to e0e229f79c 2026-08-27 21:58:32 +02:00 Compare

release-bot force-pushed release-prep/rolling from e0e229f79c to 3960ecc5e6 2026-08-27 22:19:24 +02:00 Compare

surveyor approved these changes 2026-08-27 23:40:11 +02:00

surveyor left a comment

Copy link

APPROVE — reviewed at 3960ecc5. A correct cut; two cosmetic notes, neither blocking.

Verified

Every consumed fragment reached the changelog, and the kinds match. 11 fragments deleted, 11 entries added, and each entry's section matches its filename suffix:

.added    811                                  -> ### Added      1
.changed  498, 604, 990                        -> ### Changed    3
.fixed    611, 627, 897, 914, 957, 992, 1008   -> ### Fixed      7
                                                                11 = 11

Version bump is consistent across every surface: VERSION 0.53.1 → 0.54.0, the seven reusable-*.yml pins, BUILD_BAKED_TOOLKIT_REF in all seven, both example projects, README.md, docs/integration.md. No surface left on 0.53.1 — I checked by diffing the pin lines rather than by spot-check.

CI is green on this head, read newest-row-per-context: 25 contexts, all success, covering all 12 required. (Read from .status on each row — .state is null per-row and exists only on the combined object.)

Should consider — two of eleven entries render a colour swatch

Nine entries write the issue reference bare, two wrap it in backticks:

(#498) (#604) (#990) (#611) (#627) (#897) (#914) (#957) (#992)     9  bare
(`#811`)  (`#1008`)                                                2  backticked

Forgejo parses #NNN inside a code span as a CSS colour and injects a preview swatch. Measured against this instance, with a bare-form control in the same sentence shape:

- **A cut refuses...** (`#811`)    -> color-preview" style="background-color: #811"
- **A wrapped trailer...** (`#1008`) -> color-preview" style="background-color: #1008"
- **Changelog body gate**... (#611)  -> no swatch, plain text

So the published changelog and the release notes will show a small coloured square beside those two references and not the other nine. Dropping the backticks makes all eleven render alike.

Nit in passing: trailing periods are inconsistent too — #811, #498 and #1008 end with ., the other eight do not. Same two entries, so one pass fixes both.

Disclosure — a finding I withdrew

I initially read the Fixed order (1008 before 611) as a lexical filename sort that 4-digit issue numbers had newly broken, #1008 being the first of those. Refuted before I wrote it up: entries in historical sections are not ordered by issue number in either direction — v0.50.0 runs 962, 941, 843, 931, 933, 697, … So there is no ordering convention here to violate, and the position of #1008 is not a regression.

Question, not a finding

BUILD_BAKED_TOOLKIT_REF moves 'main' → 'v0.54.0' in all seven reusables, which matches the in-line comment (auto-updated by rt prep / rt repin). What I could not see from the diff is the return trip: main currently holds 'main', so something resets it after a cut. Assuming that is reusable-release.yml's post-merge push and not something a reviewer needs to check — flagging only so the assumption is on the record rather than in my head.

**APPROVE** — reviewed at `3960ecc5`. A correct cut; two cosmetic notes, neither blocking. ## Verified **Every consumed fragment reached the changelog, and the kinds match.** 11 fragments deleted, 11 entries added, and each entry's section matches its filename suffix: ``` .added 811 -> ### Added 1 .changed 498, 604, 990 -> ### Changed 3 .fixed 611, 627, 897, 914, 957, 992, 1008 -> ### Fixed 7 11 = 11 ``` **Version bump is consistent across every surface**: `VERSION` 0.53.1 → 0.54.0, the seven `reusable-*.yml` pins, `BUILD_BAKED_TOOLKIT_REF` in all seven, both example projects, `README.md`, `docs/integration.md`. No surface left on 0.53.1 — I checked by diffing the pin lines rather than by spot-check. **CI is green on this head, read newest-row-per-context**: 25 contexts, all `success`, covering all 12 required. (Read from `.status` on each row — `.state` is null per-row and exists only on the combined object.) ## Should consider — two of eleven entries render a colour swatch Nine entries write the issue reference bare, two wrap it in backticks: ``` (#498) (#604) (#990) (#611) (#627) (#897) (#914) (#957) (#992) 9 bare (`#811`) (`#1008`) 2 backticked ``` Forgejo parses `#NNN` inside a code span as a **CSS colour** and injects a preview swatch. Measured against this instance, with a bare-form control in the same sentence shape: ``` - **A cut refuses...** (`#811`) -> color-preview" style="background-color: #811" - **A wrapped trailer...** (`#1008`) -> color-preview" style="background-color: #1008" - **Changelog body gate**... (#611) -> no swatch, plain text ``` So the published changelog and the release notes will show a small coloured square beside those two references and not the other nine. Dropping the backticks makes all eleven render alike. **Nit in passing**: trailing periods are inconsistent too — `#811`, `#498` and `#1008` end with `.`, the other eight do not. Same two entries, so one pass fixes both. ## Disclosure — a finding I withdrew I initially read the `Fixed` order (`1008` before `611`) as a lexical filename sort that 4-digit issue numbers had newly broken, `#1008` being the first of those. **Refuted before I wrote it up**: entries in historical sections are not ordered by issue number in either direction — `v0.50.0` runs 962, 941, 843, 931, 933, 697, … So there is no ordering convention here to violate, and the position of `#1008` is not a regression. ## Question, not a finding `BUILD_BAKED_TOOLKIT_REF` moves `'main'` → `'v0.54.0'` in all seven reusables, which matches the in-line comment (*auto-updated by rt prep / rt repin*). What I could not see from the diff is the return trip: `main` currently holds `'main'`, so something resets it after a cut. Assuming that is `reusable-release.yml`'s post-merge push and not something a reviewer needs to check — flagging only so the assumption is on the record rather than in my head.

bosun merged commit 3960ecc5e6 into main 2026-08-27 23:41:11 +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!1006

No description provided.