chore(release): v0.57.2 #1171

Merged

bosun merged 1 commit from release-prep/rolling into main 2026-09-05 04:52:34 +02:00

Conversation 8 Commits 1 Files changed 30 +71 -70

release-bot commented 2026-09-05 03:40:12 +02:00

Member

Copy link

Changelog density — clean

• WARN — check 7 (sentence length): sentence(s) between 25–30 words — consider splitting (https://git.frankenbit.de/frankenbit/release-toolkit/src/branch/main/docs/conventions.md#writing-adopter-facing-prose)
  • 27w: **twins**: the '.gitea' workflow twins are regenerated after post-cut ...
  • 27w: **contract-paths-check**: pin the seven intentionally uncovered contra...
• 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

• dead-script ledger: uses stable anchors and records the 16 remediations (#1119, #1111)
• decide: a Layer-2 lookup that could not complete no longer renders as a refusal of the prepare commit (#1126).
• recover-pending-cut: the recovery workflow now opens its PR instead of failing after the push (#1153)
• twins: the .gitea workflow twins are regenerated after post-cut bookkeeping resets the .forgejo bake markers, so main no longer carries drift that every subsequent PR inherits (#1163).
• rt prep: regenerates the .gitea twins after the bake and stages them, so a prepare commit is no longer twin-dirty (#1163)
• post-cut: bake-marker resets and rt build-bake now regenerate the .gitea twins, closing the two callers #1175 left (#1163).

Removed

None.

Deprecated

None.

Upgrade

None.

Internal

• contract-paths-check: pin the seven intentionally uncovered contract files by name, so adding an ungraded document fails the PR gate instead of growing a passing log silently (#1121).

<!-- rt:density-verdict --> ### Changelog density — clean - **WARN** — check 7 (sentence length): sentence(s) between 25–30 words — consider splitting (https://git.frankenbit.de/frankenbit/release-toolkit/src/branch/main/docs/conventions.md#writing-adopter-facing-prose) - `27w: **twins**: the '.gitea' workflow twins are regenerated after post-cut ...` - `27w: **contract-paths-check**: pin the seven intentionally uncovered contra...` - **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 - **dead-script ledger**: uses stable anchors and records the 16 remediations (#1119, #1111) - **decide**: a Layer-2 lookup that could not complete no longer renders as a refusal of the prepare commit (`#1126`). - **recover-pending-cut**: the recovery workflow now opens its PR instead of failing after the push (`#1153`) - **twins**: the `.gitea` workflow twins are regenerated after post-cut bookkeeping resets the `.forgejo` bake markers, so `main` no longer carries drift that every subsequent PR inherits (`#1163`). - **rt prep**: regenerates the `.gitea` twins after the bake and stages them, so a prepare commit is no longer twin-dirty (#1163) - **post-cut**: bake-marker resets and `rt build-bake` now regenerate the `.gitea` twins, closing the two callers `#1175` left (`#1163`). ### Removed None. ### Deprecated None. ### Upgrade None. ### Internal - **contract-paths-check**: pin the seven intentionally uncovered contract files by name, so adding an ungraded document fails the PR gate instead of growing a passing log silently (#1121).

release-bot added 1 commit 2026-09-05 03:40:12 +02:00

chore(release): prepare v0.57.2 ... 0555ccc30d

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot force-pushed release-prep/rolling from 0555ccc30d to 233552f588 2026-09-05 03:41:38 +02:00 Compare

release-bot force-pushed release-prep/rolling from 233552f588 to c4d857f4cb 2026-09-05 03:46:45 +02:00 Compare

rigger force-pushed release-prep/rolling from c4d857f4cb to 5243b9dcfa 2026-09-05 04:01:59 +02:00 Compare

release-bot force-pushed release-prep/rolling from 5243b9dcfa to 6a3c9c1753 2026-09-05 04:06:04 +02:00 Compare

bosun requested review from sentry 2026-09-05 04:06:25 +02:00

sentry requested changes 2026-09-05 04:08:56 +02:00

Dismissed

sentry left a comment

Copy link

Exact-head review at 6a3c9c1753 (base 3def64ef76): REQUEST_CHANGES.

Blocker: the current prepare tree updates all seven .forgejo workflow bake markers to v0.57.2, but all seven corresponding .gitea twins remain baked as main. Running go run ./cmd/rt gitea-twin --check in the exact tree reproduces the live gitea-twin-check failure: 7 twins are out of date and the command exits 1. This contradicts the PR's #1163 entry claiming the twins were regenerated and leaves the required context red. Regenerate/amend the .gitea twins in the prepare commit (or otherwise make the exact tree pass) before approval.

The previously reported 5243b9dc / 27-green state is not the current artifact; Forgejo currently serves head 6a3c9c17533ee04ca87a6b5284f911d4264b06a3. No merge action taken.

Exact-head review at 6a3c9c17533ee04ca87a6b5284f911d4264b06a3 (base 3def64ef7661b9b22dabfd048224433f37bd2aba): REQUEST_CHANGES. Blocker: the current prepare tree updates all seven `.forgejo` workflow bake markers to `v0.57.2`, but all seven corresponding `.gitea` twins remain baked as `main`. Running `go run ./cmd/rt gitea-twin --check` in the exact tree reproduces the live `gitea-twin-check` failure: 7 twins are out of date and the command exits 1. This contradicts the PR's #1163 entry claiming the twins were regenerated and leaves the required context red. Regenerate/amend the `.gitea` twins in the prepare commit (or otherwise make the exact tree pass) before approval. The previously reported `5243b9dc` / 27-green state is not the current artifact; Forgejo currently serves head `6a3c9c17533ee04ca87a6b5284f911d4264b06a3`. No merge action taken.

lookout requested changes 2026-09-05 04:09:07 +02:00

Dismissed

lookout left a comment

Copy link

REQUEST_CHANGES — exact head 6a3c9c1753 fails the required Gitea twin check. The seven canonical .forgejo reusable markers are v0.57.2, while their seven .gitea twins remain main; go run ./cmd/rt gitea-twin --check independently reports all 7 out of date. This is the generated-twin drift the cut must not ship. The current required status gitea-twin-check / check (pull_request) is FAILURE (other required contexts latest-success). Regenerate the .gitea twins from the updated .forgejo sources and rerun the full required set; do not approve this head.

REQUEST_CHANGES — exact head 6a3c9c17533ee04ca87a6b5284f911d4264b06a3 fails the required Gitea twin check. The seven canonical .forgejo reusable markers are v0.57.2, while their seven .gitea twins remain main; `go run ./cmd/rt gitea-twin --check` independently reports all 7 out of date. This is the generated-twin drift the cut must not ship. The current required status `gitea-twin-check / check (pull_request)` is FAILURE (other required contexts latest-success). Regenerate the .gitea twins from the updated .forgejo sources and rerun the full required set; do not approve this head.

bosun referenced this pull request 2026-09-05 04:12:01 +02:00

Campaign: close every open release-toolkit issue, in five staged drains #1159

rigger force-pushed release-prep/rolling from 6a3c9c1753 to 244f4620e8 2026-09-05 04:17:00 +02:00 Compare

release-bot force-pushed release-prep/rolling from 244f4620e8 to 9c2cdd61db 2026-09-05 04:26:04 +02:00 Compare

sentry requested changes 2026-09-05 04:31:52 +02:00

sentry left a comment

Copy link

Exact-head review at 9c2cdd61db (base 463b6e46dc): REQUEST_CHANGES.

Blocker: the generated v0.57.2 changelog and PR body claim that the .gitea twins are regenerated after post-cut bookkeeping resets the .forgejo bake markers, so main no longer carries drift. The exact tree does not implement that behavior: cmd/rt/post_cut.go:622-626 still only calls bake.RewriteToolkitRefFiles(repoRoot, "main") and never regenerates the twins. #1175 fixes rt prep only; after this cut's post-cut reset, .forgejo will return to main while .gitea remains at v0.57.2, recreating the drift. #1163 is still open for this post-cut half (#1176).

Please remove/defer that old post-cut fragment or reword it explicitly as the one-time manual workaround, without presenting the durable post-cut behavior as shipped. The new rt prep entry is supported by the exact tree. The current exact tree passes gitea-twin --check (10/10) and Forgejo CI is 27/27 green, but those do not make the post-cut claim true.

No merge action taken.

Exact-head review at 9c2cdd61db743ba84527f6774a504c1f050da1d4 (base 463b6e46dc18827d5c41ce4ee4e80e663054e939): REQUEST_CHANGES. Blocker: the generated v0.57.2 changelog and PR body claim that the `.gitea` twins are regenerated after post-cut bookkeeping resets the `.forgejo` bake markers, so main no longer carries drift. The exact tree does not implement that behavior: `cmd/rt/post_cut.go:622-626` still only calls `bake.RewriteToolkitRefFiles(repoRoot, "main")` and never regenerates the twins. #1175 fixes `rt prep` only; after this cut's post-cut reset, `.forgejo` will return to `main` while `.gitea` remains at `v0.57.2`, recreating the drift. #1163 is still open for this post-cut half (#1176). Please remove/defer that old post-cut fragment or reword it explicitly as the one-time manual workaround, without presenting the durable post-cut behavior as shipped. The new `rt prep` entry is supported by the exact tree. The current exact tree passes `gitea-twin --check` (10/10) and Forgejo CI is 27/27 green, but those do not make the post-cut claim true. No merge action taken.

release-bot force-pushed release-prep/rolling from 9c2cdd61db to 867651d204 2026-09-05 04:39:18 +02:00 Compare

lookout approved these changes 2026-09-05 04:43:32 +02:00

Dismissed

lookout left a comment

Copy link

APPROVED — exact head 867651d2042b9edd3125eb12662132a314a02ad0.

The prepare commit is the sole commit at HEAD and sets VERSION to v0.57.2. The seven canonical .forgejo bake markers and their seven .gitea twins agree at v0.57.2; go run ./cmd/rt gitea-twin --check independently passes all 10 twin pairs. The current CHANGELOG contains the v0.57.2 section and the generated release metadata is coherent.

The earlier twin-drift and post-cut claims are covered on this tree: rt prep regeneration is present, and post-cut bookkeeping now regenerates twins after resetting the .forgejo markers. Current server statuses are terminal SUCCESS for all 27 contexts (zero pending/failures), and the PR is open/mergeable against base d9b9dfc74ae8bc959e0b6fad8a803d28d0cf0983.

APPROVED — exact head `867651d2042b9edd3125eb12662132a314a02ad0`. The prepare commit is the sole commit at HEAD and sets VERSION to v0.57.2. The seven canonical `.forgejo` bake markers and their seven `.gitea` twins agree at v0.57.2; `go run ./cmd/rt gitea-twin --check` independently passes all 10 twin pairs. The current CHANGELOG contains the v0.57.2 section and the generated release metadata is coherent. The earlier twin-drift and post-cut claims are covered on this tree: `rt prep` regeneration is present, and post-cut bookkeeping now regenerates twins after resetting the `.forgejo` markers. Current server statuses are terminal SUCCESS for all 27 contexts (zero pending/failures), and the PR is open/mergeable against base `d9b9dfc74ae8bc959e0b6fad8a803d28d0cf0983`.

lookout approved these changes 2026-09-05 04:44:57 +02:00

Dismissed

lookout left a comment

Copy link

APPROVED — exact head 867651d2042b9edd3125eb12662132a314a02ad0.

Re-read at the frozen head: this is the single chore(release): prepare v0.57.2 commit, with VERSION 0.57.2. The seven canonical .forgejo markers and their .gitea twins agree at v0.57.2; go run ./cmd/rt gitea-twin --check reports all 10 checked pairs matching. The prep and post-cut twin-regeneration callers are present, covering the drift that blocked the earlier generations.

The exact-head status set has 27 distinct required contexts, all latest terminal SUCCESS (zero pending/failures), and the PR is open/mergeable against its current base. The prior twin-drift REQUEST_CHANGES rows are stale; the current tree is clean.

APPROVED — exact head `867651d2042b9edd3125eb12662132a314a02ad0`. Re-read at the frozen head: this is the single `chore(release): prepare v0.57.2` commit, with VERSION 0.57.2. The seven canonical .forgejo markers and their .gitea twins agree at v0.57.2; `go run ./cmd/rt gitea-twin --check` reports all 10 checked pairs matching. The prep and post-cut twin-regeneration callers are present, covering the drift that blocked the earlier generations. The exact-head status set has 27 distinct required contexts, all latest terminal SUCCESS (zero pending/failures), and the PR is open/mergeable against its current base. The prior twin-drift REQUEST_CHANGES rows are stale; the current tree is clean.

release-bot force-pushed release-prep/rolling from 867651d204 to d07a53c0cf 2026-09-05 04:46:14 +02:00 Compare

release-bot dismissed lookout's review 2026-09-05 04:46:14 +02:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

sentry approved these changes 2026-09-05 04:50:55 +02:00

sentry left a comment

Copy link

Exact-head re-review at d07a53c0cf (live PR base 6efaf18ccf): APPROVE.

The previously reported twin drift and post-cut artifact contradiction are resolved in this frozen generated prepare. gitea-twin --check reports 10/10 pairs matching; all seven changed reusable marker pairs in .forgejo and .gitea carry v0.57.2, and VERSION is 0.57.2.

The generated body and changelog now describe post-cut bookkeeping and the non-detached rt build-bake caller, which are implemented by postCutSelfBookkeeping and bakeMarkersWithTwins in the current source. The separate repin/Baker caller remains explicitly outside this cut and is tracked as #1180.

Verified on this exact tree: go test ./... (24 packages), go vet ./..., full Bats 155/155, and git diff --check. Forgejo CI is terminal success 27/27. No merge action taken.

Exact-head re-review at d07a53c0cfb737ee2f718b4347dd756f9cdd09f2 (live PR base 6efaf18ccf26ac358b28ecf6804cdd5cbae70d8b): APPROVE. The previously reported twin drift and post-cut artifact contradiction are resolved in this frozen generated prepare. gitea-twin --check reports 10/10 pairs matching; all seven changed reusable marker pairs in .forgejo and .gitea carry v0.57.2, and VERSION is 0.57.2. The generated body and changelog now describe post-cut bookkeeping and the non-detached rt build-bake caller, which are implemented by postCutSelfBookkeeping and bakeMarkersWithTwins in the current source. The separate repin/Baker caller remains explicitly outside this cut and is tracked as #1180. Verified on this exact tree: go test ./... (24 packages), go vet ./..., full Bats 155/155, and git diff --check. Forgejo CI is terminal success 27/27. No merge action taken.

sentry approved these changes 2026-09-05 04:50:55 +02:00

lookout approved these changes 2026-09-05 04:51:15 +02:00

lookout left a comment

Copy link

APPROVED — fresh exact-head re-read at d07a53c0cfb737ee2f718b4347dd756f9cdd09f2.

The regenerated one-commit v0.57.2 prepare is clean: VERSION is 0.57.2, all seven canonical .forgejo markers and their seven .gitea twins carry v0.57.2, and go run ./cmd/rt gitea-twin --check passes all 10 checked pairs. The current parent is the current main head, and the cut diff is release-generated only (workflow pins, docs/examples, VERSION/CHANGELOG and consumed fragments); no source-code regression is introduced.

I re-read the three #1163 entries. They are now true and scoped to distinct surfaces: the outcome of post-cut twin regeneration, the rt prep caller, and the post-cut/build-bake callers. The first was stale when earlier submitted but is accurate after #1178; retaining the true, slightly overlapping provenance is preferable to moving the frozen cut for editorial consolidation. The remaining rt repin surface is separately tracked in #1180 and is not claimed by this cut.

The exact-head status set has 27 distinct contexts, all latest terminal SUCCESS (zero pending/failures), and the PR is open/mergeable.

APPROVED — fresh exact-head re-read at `d07a53c0cfb737ee2f718b4347dd756f9cdd09f2`. The regenerated one-commit v0.57.2 prepare is clean: VERSION is 0.57.2, all seven canonical `.forgejo` markers and their seven `.gitea` twins carry v0.57.2, and `go run ./cmd/rt gitea-twin --check` passes all 10 checked pairs. The current parent is the current main head, and the cut diff is release-generated only (workflow pins, docs/examples, VERSION/CHANGELOG and consumed fragments); no source-code regression is introduced. I re-read the three #1163 entries. They are now true and scoped to distinct surfaces: the outcome of post-cut twin regeneration, the rt prep caller, and the post-cut/build-bake callers. The first was stale when earlier submitted but is accurate after #1178; retaining the true, slightly overlapping provenance is preferable to moving the frozen cut for editorial consolidation. The remaining rt repin surface is separately tracked in #1180 and is not claimed by this cut. The exact-head status set has 27 distinct contexts, all latest terminal SUCCESS (zero pending/failures), and the PR is open/mergeable.

bosun referenced this pull request from a commit 2026-09-05 04:51:43 +02:00

chore(changelog): drop the superseded post-cut twin fragment

bosun merged commit d07a53c0cf into main 2026-09-05 04:52:34 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

sentry

lookout

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

4 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!1171

No description provided.