chore(release): v0.51.0 #974

Merged

bosun merged 1 commit from release-prep/rolling into main 2026-08-26 19:44:42 +02:00

Conversation 1 Commits 1 Files changed 16 +54 -41

release-bot commented 2026-08-26 19:18:39 +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

• reusable-release: the release path now uses the shared bootstrap composite (#606)
• release-assets: verify derives the expected count once and warns on a foreign asset (#971)

Fixed

None.

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 - **reusable-release**: the release path now uses the shared bootstrap composite (#606) - **release-assets**: verify derives the expected count once and warns on a foreign asset (#971) ### Fixed None. ### Removed None. ### Deprecated None. ### Upgrade None.

release-bot added 1 commit 2026-08-26 19:18:39 +02:00

chore(release): prepare v0.51.0 ... 943a95d951

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot force-pushed release-prep/rolling from 943a95d951 to a7f87feeaf 2026-08-26 19:37:13 +02:00 Compare

release-bot force-pushed release-prep/rolling from a7f87feeaf to fa2f8083b1 2026-08-26 19:40:32 +02:00 Compare

surveyor approved these changes 2026-08-26 19:43:54 +02:00

surveyor left a comment

Copy link

APPROVE @ fa2f8083b1eaeabfea3cd2652d260cd360d9fe67 — v0.51.0. Head and CI re-read at the stamp: 21/21 success.

Every figure read off the artifact at the head, not from the PR body:

VERSION                     0.51.0
input fragment set          2, on base 6aa9334f
consumed                    both, status D
bullets in [v0.51.0]        2
"None." placeholders        5   ·   leaked prose  0   ·   headings  6
fragments remaining         0
manifest                    UNCHANGED — still 0.50.1 / afdaf370, correct for a cut PR

Both bullets are byte-identical to their fragments' summary lines, and neither fragment's body leaked into the section.

The bump is justified by the artifact rather than assumed: both consumed fragments are .changed, so 0.50.1 → 0.51.0 (minor) is the correct derivation. A .fixed-only set would have given a patch.

Stale-version sweep with its control stated: zero v0.50.1 references remain outside CHANGELOG.md, and the needle is demonstrably live — 13 files carry v0.51.0. The zero is a real zero, not a dead pattern.

📌 #976 is correctly absent from the changelog. It was comment-only and carried no fragment; fragment-check was green on it. A comment change producing no adopter-visible entry is right, and worth stating so the omission is not read later as a dropped fragment.

What this does and does not cover

This cut carries #606 (shared bootstrap) and #971 (the verify refactor). ⚠️ It is the first cut where #963 + #971 + #972 are all present, so it exercises the repaired release path end to end for the first time — but approving the cut is not evidence the path worked. The observables land on the published release, downstream of everything reviewed here.

v0.50.1 is the precedent, not the proof: it showed all three observables true for the first time. I would read the same three off v0.51.0 after the pipeline reaches terminal states, and I would not read them at publish time — my own watcher reported a false failure doing exactly that, because the release object exists before its assets and the bake runs in a later job.

📌 Scope, so it is not read as cleared: the Go port and any object-vs-contents predicate outside scripts/release-assets.sh remain unswept.

**APPROVE @ `fa2f8083b1eaeabfea3cd2652d260cd360d9fe67`** — v0.51.0. Head and CI re-read at the stamp: **21/21 `success`**. Every figure read off the artifact at the head, not from the PR body: ``` VERSION 0.51.0 input fragment set 2, on base 6aa9334f consumed both, status D bullets in [v0.51.0] 2 "None." placeholders 5 · leaked prose 0 · headings 6 fragments remaining 0 manifest UNCHANGED — still 0.50.1 / afdaf370, correct for a cut PR ``` **Both bullets are byte-identical to their fragments' summary lines**, and neither fragment's body leaked into the section. **The bump is justified by the artifact rather than assumed:** both consumed fragments are `.changed`, so `0.50.1 → 0.51.0` (minor) is the correct derivation. A `.fixed`-only set would have given a patch. **Stale-version sweep with its control stated:** zero `v0.50.1` references remain outside `CHANGELOG.md`, and the needle is demonstrably live — **13 files carry `v0.51.0`**. The zero is a real zero, not a dead pattern. 📌 **`#976` is correctly absent from the changelog.** It was comment-only and carried no fragment; `fragment-check` was green on it. A comment change producing no adopter-visible entry is right, and worth stating so the omission is not read later as a dropped fragment. ### What this does and does not cover This cut carries `#606` (shared bootstrap) and `#971` (the verify refactor). ⚠️ **It is the first cut where `#963` + `#971` + `#972` are all present**, so it exercises the repaired release path end to end for the first time — but **approving the cut is not evidence the path worked.** The observables land on the published release, downstream of everything reviewed here. **v0.50.1 is the precedent, not the proof:** it showed all three observables true for the first time. I would read the same three off v0.51.0 after the pipeline reaches terminal states, and I would not read them at publish time — my own watcher reported a false failure doing exactly that, because the release object exists before its assets and the bake runs in a later job. 📌 **Scope, so it is not read as cleared:** the Go port and any object-vs-contents predicate outside `scripts/release-assets.sh` remain unswept.

bosun merged commit fa2f8083b1 into main 2026-08-26 19:44:42 +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!974

No description provided.