fix(release): build the pipeline rt before the step that runs it (#1112) #1154

Merged

alex merged 1 commit from i/1112-build-rt-before-first-use into main 2026-09-05 01:44:26 +02:00

Conversation 0 Commits 1 Files changed 2 +23 -12

quartermaster commented 2026-09-05 00:54:39 +02:00

Owner

• Copy link
• Copy Markdown

measure and prepare release assets invokes $RUNNER_TEMP/rt-pipeline, and build the pipeline rt sat one step below it. Exit 127 on every cut since #1112 landed.

v0.56.1  2026-08-30  3 assets   (predates #1112)
v0.57.0  2026-09-05  0 assets   published, live, unusable

The step's own comment already said "reused by both call sites below" — one call site was above it. This moves the build above its first caller and corrects the comment to name the ordering as load-bearing, since the step otherwise reads as independent.

Not the runner. caymans-fedora has stale registry credentials and dies at the image pull — a real, separate defect, tracked with @bosun. The dispatched re-run landed on alcatraz-runner and failed here instead, which is how this surfaced.

What this does NOT do: it does not republish v0.57.0. That needs a workflow_dispatch at main with tag=v0.57.0 once this is merged — the operator is firing that himself.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LUEggQMJjaizj2nFVofeyH

`measure and prepare release assets` invokes `$RUNNER_TEMP/rt-pipeline`, and `build the pipeline rt` sat one step **below** it. Exit 127 on every cut since #1112 landed. ``` v0.56.1 2026-08-30 3 assets (predates #1112) v0.57.0 2026-09-05 0 assets published, live, unusable ``` The step's own comment already said *"reused by both call sites below"* — one call site was above it. This moves the build above its first caller and corrects the comment to name the ordering as load-bearing, since the step otherwise reads as independent. **Not the runner.** `caymans-fedora` has stale registry credentials and dies at the image pull — a real, separate defect, tracked with @bosun. The dispatched re-run landed on `alcatraz-runner` and failed **here** instead, which is how this surfaced. **What this does NOT do:** it does not republish v0.57.0. That needs a `workflow_dispatch` at `main` with `tag=v0.57.0` once this is merged — the operator is firing that himself. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01LUEggQMJjaizj2nFVofeyH

quartermaster referenced this pull request 2026-09-05 01:15:29 +02:00

chore(ci): regenerate the .gitea twins stale since v0.57.0 #1155

alex force-pushed i/1112-build-rt-before-first-use from 744ee0d250 to f182fd93fe 2026-09-05 01:16:21 +02:00 Compare

quartermaster referenced this pull request from a commit 2026-09-05 01:37:57 +02:00

fix(changelog): the twins fragment needs an issue reference (#1112)

quartermaster referenced this pull request 2026-09-05 01:37:57 +02:00

fix(changelog): the twins fragment needs an issue reference (#1112) #1156

alex force-pushed i/1112-build-rt-before-first-use from f182fd93fe to 226cc806de 2026-09-05 01:40:23 +02:00 Compare

alex merged commit 226cc806de into main 2026-09-05 01:44:26 +02:00

alex deleted branch i/1112-build-rt-before-first-use 2026-09-05 01:44:26 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

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

epic

Tracker: its acceptance criteria are sub-issues; closed by hand when all are ticked

  

kind

feature

New feature or capability

  

loop/paused

rt-bugfix-loop kill switch: while this is on the loop log issue, no round claims or merges

  

mirror-drift

Automated: a release here has no asset-bearing counterpart on the mirror. One tracker per drift episode; the check never reopens a closed one (#1586)

  

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+

  

status

blocked

Cannot start until a named dependency resolves

No labels

bump

major

bump

minor

bump

patch

kind

bug

kind

chore

kind

docs

kind

epic

kind

feature

loop/paused

mirror-drift

priority

critical

priority

high

priority

low

priority

medium

size

L

size

M

size

S

size

XL

status

blocked

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!1154

No description provided.