fix(changelog): fold the interrupted v0.57.0 cut back under [Unreleased] #1151

Merged

alex merged 1 commit from recover-pending-cut/0.57.0 into main 2026-09-04 22:19:25 +02:00

Conversation 1 Commits 1 Files changed 1 -2

bosun commented 2026-09-04 22:15:07 +02:00

Owner

Copy link

Recovery (B) for the interrupted v0.57.0 cut. The stranded section is folded back under [Unreleased]; rt decide will then route to update and re-prepare (#1128).

This is not auto-merged and must not be. Recovery (B) applied to a published release orphans it. rt established before writing that no tag or release exists for v0.57.0 — confirmed independently here, from rt decide's own refusal on main:

reason=pending_cut
pending_version=0.57.0
pending_prep_sha=4a3427048ea02aa9e9582da3208bbeb70907925d
pending_tag_exists=false
pending_release_published=absent

Read the diff and confirm that still holds before merging. Recovery (A) — completing a release that already exists — is not reachable from this path and stays manual.

What the branch actually contains

main    ## [Unreleased]  (21)  →  ## [v0.57.0] - 2026-08-29  (23)
branch  ## [Unreleased]  (21)  →  ## [v0.56.1] - 2026-08-28  (60)

The v0.57.0 heading is gone from the released list and its entries sit under [Unreleased]. Verified by reading both files from the server, not from the workflow's own report.

⚠️ Why this PR was opened by hand

reusable-recover-pending-cut.yml did the recovery correctly and then failed to open this PR:

recovered: v0.57.0 is back under [Unreleased] in CHANGELOG.md
Switched to a new branch 'recover-pending-cut/0.57.0'
remote: Create a new pull request for 'recover-pending-cut/0.57.0'   ← branch pushed
rt default-branch: required flag(s) "owner", "repo" not set          ← then exit 2

rt default-branch marks both flags required; the workflow calls it bare at :301, while already holding OWNER and REPO at :143-144 for the PR call it never reached. reusable-release.yml:770 has the correct form:

rt default-branch --owner "$OWNER" --repo "$REPO"

That is a separate one-line defect in the workflow and is not part of this PR — this PR is the recovery itself. The commit on this branch is the workflow's own, unmodified.

Anchor

Recovery run 10940. Workflow defect found by @bosun reading the job log after the operator reported the failure; the recovery verb (#1130) and the reusable workflow (#1135) both did their part.

Recovery (B) for the interrupted **v0.57.0** cut. The stranded section is folded back under `[Unreleased]`; `rt decide` will then route to update and re-prepare (#1128). **This is not auto-merged and must not be.** Recovery (B) applied to a *published* release orphans it. `rt` established before writing that no tag or release exists for v0.57.0 — confirmed independently here, from `rt decide`'s own refusal on main: ``` reason=pending_cut pending_version=0.57.0 pending_prep_sha=4a3427048ea02aa9e9582da3208bbeb70907925d pending_tag_exists=false pending_release_published=absent ``` **Read the diff and confirm that still holds before merging.** Recovery (A) — completing a release that already exists — is not reachable from this path and stays manual. ## What the branch actually contains ``` main ## [Unreleased] (21) → ## [v0.57.0] - 2026-08-29 (23) branch ## [Unreleased] (21) → ## [v0.56.1] - 2026-08-28 (60) ``` The v0.57.0 heading is gone from the released list and its entries sit under `[Unreleased]`. Verified by reading both files from the server, not from the workflow's own report. ## ⚠️ Why this PR was opened by hand `reusable-recover-pending-cut.yml` **did the recovery correctly and then failed to open this PR:** ``` recovered: v0.57.0 is back under [Unreleased] in CHANGELOG.md Switched to a new branch 'recover-pending-cut/0.57.0' remote: Create a new pull request for 'recover-pending-cut/0.57.0' ← branch pushed rt default-branch: required flag(s) "owner", "repo" not set ← then exit 2 ``` `rt default-branch` marks both flags required; the workflow calls it bare at `:301`, **while already holding `OWNER` and `REPO` at `:143-144`** for the PR call it never reached. `reusable-release.yml:770` has the correct form: ``` rt default-branch --owner "$OWNER" --repo "$REPO" ``` That is a separate one-line defect in the workflow and is **not** part of this PR — this PR is the recovery itself. The commit on this branch is the workflow's own, unmodified. ## Anchor Recovery run `10940`. Workflow defect found by @bosun reading the job log after the operator reported the failure; the recovery verb (#1130) and the reusable workflow (#1135) both did their part.

bosun added 1 commit 2026-09-04 22:15:07 +02:00

fix(changelog): fold the interrupted v0.57.0 cut back under [Unreleased] ... 510ee36625

rt recover-pending-cut, recovery (B) of docs/integration.md
section Cut-cancellation recovery. The cut was prepared and never tagged,
leaving the section stranded above the manifest; rt decide now routes to
update and re-prepares (#1128).

Opened as a PR rather than pushed: the choice to apply (B) is a human one,
and a PR is where that choice is recorded.

alex approved these changes 2026-09-04 22:19:21 +02:00

alex merged commit 510ee36625 into main 2026-09-04 22:19:25 +02:00

alex deleted branch recover-pending-cut/0.57.0 2026-09-04 22:19:25 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

alex

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

No description provided.