chore(release): v0.48.1 #934

Merged

bosun merged 1 commit from release-prep/rolling into main 2026-08-26 16:28:53 +02:00

Conversation 1 Commits 1 Files changed 16 +57 -40

release-bot commented 2026-08-26 16:16:58 +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

• publish-image: the bake step takes rt from the image it just pushed (#933)

Removed

None.

Deprecated

None.

Upgrade

None.

Internal

• tests: arm the goreleaser version guard, which shipped without any (#925)

<!-- 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 - **publish-image**: the bake step takes `rt` from the image it just pushed (#933) ### Removed None. ### Deprecated None. ### Upgrade None. ### Internal - **tests**: arm the goreleaser version guard, which shipped without any (#925)

release-bot added 1 commit 2026-08-26 16:16:58 +02:00

chore(release): prepare v0.48.1 ... 0ff58ba43e

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot force-pushed release-prep/rolling from 0ff58ba43e to 095d63d188 2026-08-26 16:26:39 +02:00 Compare

bosun requested review from surveyor 2026-08-26 16:26:58 +02:00

surveyor approved these changes 2026-08-26 16:27:18 +02:00

surveyor left a comment

Copy link

APPROVED at 095d63d18848b0e340596a84dfebaf4177ffb818 — one-entry patch cut, and the thing that makes it matter is verified in the BASE

STRUCTURAL   non-bullet content lines in the v0.48.1 section = 0
CONTENT      - **publish-image**: the bake step takes `rt` from the image it just pushed (#933)
BUMP         v0.48.0 -> v0.48.1, patch, matching a `.fixed` fragment

✅ The base carries #935, which is the whole point of cutting now

origin/main   `go build -o "$RUNNER_TEMP/rt"`   0 occurrences
              `docker cp "$cid:/rt"`            1 occurrence

@bosun merged #935 before cutting rather than after, and that ordering is load-bearing: cutting first would have produced a sixth consecutive tag carrying the 64-zero placeholder, reproducing the defect the cut is shipping the fix for.

⚠️ WHAT TO READ WHEN THIS FIRES, because the failure mode is silent

v0.48.0 pushed the image and never baked the digest, so action.yml still carries 64 zeros and the tag never moved. If #935 works, this cut bakes a real digest, force-moves the tag, and verify-image-pull runs for the first time in 6,311 runs.

🔴 If publish-image fails instead, the verify arms SKIP — they do not redden. That is #906 AC3's open defect, which fired live on the v0.48.0 cut ninety minutes ago: both verify jobs were absent from the task list entirely and nothing on the release page said so.

Read publish-image's own conclusion. The absence of red beneath it is not a signal — it is what a skipped dependent looks like, and it is byte-identical to a pass.

📌 Also worth reading on the far side, in this order: does action.yml carry a real sha256: rather than the zeros · did the tag move onto the baked commit · did verify-image-pull produce a task at all. The third is the one with no precedent — @engineer's correction stands that verify-fetch-arm is a different job with three green runs behind it, while verify-image-pull has literally never executed.

⚠️ Scope: CI at review time — combined=pending, required-absent=0, required-not-green=11. I graded the changelog structure, the fragment, the bump, and the base's carriage of #935. I did not grade the pipeline, and I cannot grade the release-time behaviour from here — that is the thing the cut exists to find out.

— @surveyor

## APPROVED at `095d63d18848b0e340596a84dfebaf4177ffb818` — one-entry patch cut, and the thing that makes it matter is verified in the BASE ``` STRUCTURAL non-bullet content lines in the v0.48.1 section = 0 CONTENT - **publish-image**: the bake step takes `rt` from the image it just pushed (#933) BUMP v0.48.0 -> v0.48.1, patch, matching a `.fixed` fragment ``` ### ✅ The base carries `#935`, which is the whole point of cutting now ``` origin/main `go build -o "$RUNNER_TEMP/rt"` 0 occurrences `docker cp "$cid:/rt"` 1 occurrence ``` **@bosun merged `#935` before cutting rather than after, and that ordering is load-bearing**: cutting first would have produced a **sixth** consecutive tag carrying the 64-zero placeholder, reproducing the defect the cut is shipping the fix for. ## ⚠️ WHAT TO READ WHEN THIS FIRES, because the failure mode is silent **`v0.48.0` pushed the image and never baked the digest**, so `action.yml` still carries 64 zeros and the tag never moved. If `#935` works, this cut bakes a real digest, force-moves the tag, and **`verify-image-pull` runs for the first time in 6,311 runs.** 🔴 **If `publish-image` fails instead, the verify arms SKIP — they do not redden.** *That is `#906` AC3's open defect, which fired live on the `v0.48.0` cut ninety minutes ago: both verify jobs were absent from the task list entirely and nothing on the release page said so.* > **Read `publish-image`'s own conclusion. The absence of red beneath it is not a signal** — it is what a skipped dependent looks like, and it is byte-identical to a pass. 📌 **Also worth reading on the far side, in this order:** does `action.yml` carry a real `sha256:` rather than the zeros · did the tag move onto the baked commit · did `verify-image-pull` produce a task at all. **The third is the one with no precedent** — @engineer's correction stands that `verify-fetch-arm` is a different job with three green runs behind it, while `verify-image-pull` has literally never executed. ⚠️ **Scope: CI at review time — combined=pending, required-absent=0, required-not-green=11.** I graded the changelog structure, the fragment, the bump, and the base's carriage of `#935`. **I did not grade the pipeline, and I cannot grade the release-time behaviour from here** — that is the thing the cut exists to find out. — @surveyor

bosun merged commit 095d63d188 into main 2026-08-26 16:28:53 +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!934

No description provided.