chore(release): v0.66.0 #1549

Merged

alex merged 1 commit from release-prep/rolling into main 2026-10-05 20:06:23 +02:00

Conversation 3 Commits 1 Files changed 23 +47 -24

release-bot commented 2026-10-05 19:59:44 +02:00

Member

• Copy link
• Copy Markdown

Cut-time changelog gates - clean

• PASS - register-check: no register drift in [v0.66.0]
• PASS - check 1 (header): version=0.66.0 date=2026-10-05
• PASS - check 2 (sections): all standard sections present (Added Changed Fixed Removed Deprecated Upgrade)
• PASS - check 3 (forward-refs): no version pins above 0.66.0
• PASS - check 4 (length): body is 209 chars (soft ceiling 5000)
• PASS - check 5 (style): all sections consistent (all-bullet or all-prose)
• PASS - check 6 (duplicates): no duplicate version sections in whole CHANGELOG.md; no duplicate ### Section headers in newest section
• 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 rt compose-verify, the cut-time preflight, run on the CHANGELOG this prep wrote. It carries no authority: the cut re-runs it against the file as it stands then, and this branch is recreated from main on every compose.

Added

• pr gates: reusable-pr-gates.yml runs every PR gate from one pr.yml and one pin (#1541)

Changed

None.

Fixed

None.

Removed

None.

Deprecated

None.

Upgrade

None.

<!-- rt:density-verdict --> ### Cut-time changelog gates - clean - **PASS** - register-check: no register drift in [v0.66.0] - **PASS** - check 1 (header): version=0.66.0 date=2026-10-05 - **PASS** - check 2 (sections): all standard sections present (Added Changed Fixed Removed Deprecated Upgrade) - **PASS** - check 3 (forward-refs): no version pins above 0.66.0 - **PASS** - check 4 (length): body is 209 chars (soft ceiling 5000) - **PASS** - check 5 (style): all sections consistent (all-bullet or all-prose) - **PASS** - check 6 (duplicates): no duplicate version sections in whole CHANGELOG.md; no duplicate ### Section headers in newest section - **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 `rt compose-verify`, the cut-time preflight, run on the CHANGELOG this prep wrote._ _It carries no authority: the cut re-runs it against the file as it stands then, and this branch is recreated from `main` on every compose._ <!-- /rt:density-verdict --> ### Added - **pr gates**: `reusable-pr-gates.yml` runs every PR gate from one `pr.yml` and one pin (#1541) ### Changed None. ### Fixed None. ### Removed None. ### Deprecated None. ### Upgrade None.

release-bot added 1 commit 2026-10-05 19:59:44 +02:00

chore(release): prepare v0.66.0 ... 57c71b619b

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot requested review from surveyor 2026-10-05 19:59:45 +02:00

claude referenced this pull request from frankenbit/cellblock 2026-10-05 20:01:20 +02:00

chore(ci): move the release-toolkit PR gates into one pr.yml and bump the pin past the gate-removal cut #181

claude referenced this pull request from frankenbit/purser 2026-10-05 20:01:21 +02:00

chore(ci): move the release-toolkit PR gates into one pr.yml and bump the pin past the gate-removal cut #63

claude referenced this pull request 2026-10-05 20:01:39 +02:00

chore(workflows)!: remove the six single-gate reusables, their wrappers and twins after reusable-pr-gates.yml lands, and cut the next minor #1542

claude referenced this pull request 2026-10-05 20:01:39 +02:00

chore(ci): one PR-gates reusable and fewer toolkit-self jobs, because the runner is down to one slot (#1304's hold condition) #1530

claude reviewed 2026-10-05 20:05:21 +02:00

claude left a comment

• Copy link
• Copy Markdown

Verdict: APPROVE at 57c71b619b

Summary: the cut is clean and additive. v0.66.0 adds reusable-pr-gates.yml and removes nothing. The bake rewrites all 20 markers, the new reusable on both providers included, and the CHANGELOG carries exactly the one fragment. The release-prep/ exemption from #1540 ran live for the first time and logged EXEMPT. Verified at source (AGENTS.md section 6).

Head pinned with rt review-submit-check (rc=0, READY) immediately before this review. Base 855b34e is still live main's tip. One commit, 57c71b6 chore(release): prepare v0.66.0, by release-bot.

1. CHANGELOG and VERSION

• VERSION: 0.65.0 becomes 0.66.0.
• ## [v0.66.0] - 2026-10-05: Added holds exactly one bullet, the header line of changelog.d/1541-reusable-pr-gates.added.md. Changed, Fixed, Removed, Deprecated and Upgrade each read None.
• The fragment is deleted in this PR. It was the only fragment on the base: main's changelog.d/ held .keep, .template.md and that file. So no base fragment survives the cut (the #1305 shape), and the load-bearing .keep stays (AGENTS.md section 12).
• The fragment's body paragraph is not in CHANGELOG.md. That matches existing behaviour: v0.65.0 (c68b696) also rendered only each fragment's header line, from fragments that carried bodies. It is not a defect of this cut.
• No removal: nothing else is deleted, and no workflow file changes beyond its marker.

2. The bake: all 20 markers, the marker line the only change

git diff 855b34e...57c71b6 over .forgejo/workflows and .gitea/workflows gives exactly 20 removed and 20 added lines, all identical:

-          BUILD_BAKED_TOOLKIT_REF: 'main'  # release-toolkit-build-ref (auto-updated by rt prep / rt repin)
+          BUILD_BAKED_TOOLKIT_REF: 'v0.66.0'  # release-toolkit-build-ref (auto-updated by rt prep / rt repin)

That covers 10 reusables on each provider: ac-closure, changelog-body, changelog-fragment, manifest, pr-gates, prepared-uncut, recover-pending-cut, register, release and workflow-parse. A grep over every workflow file at head finds no release-toolkit-build-ref marker with any value other than 'v0.66.0'. So reusable-pr-gates.yml@v0.66.0 carries its own version. A tag-pinned adopter's D6 resolve takes the "tag pin, baked tag" arm, not the #1222 fallback or the new refusal. rt post-cut resets main to 'main' afterwards.

3. The release-prep/ exemption (#1540), first live run

toolkit-self-gates (run 19848, job 0, commit 57c71b619b), g10:

check-self-bootstrap: EXEMPT on the release-prep rolling PR (release-prep/rolling, #304).
check-self-bootstrap: the merge fires push:main, where check-self-bootstrap.yml runs the full check.

Attest reads EXEMPT: g10 recorded an exemption, which EXEMPTABLE_GATE_IDS allows, then 15 of 15. The other moved gates ran normally:

• g11: twins match;
• g12: #1157 still refused;
• g13: prep-order-check: PASS;
• g14: digest PASS.

4. CI, read in job logs (Axis C)

All 32 statuses are success.

• pr / plan, and run every gate when combined (run 19844, job 1): it resolved the toolkit ref to main (source=toolkit-self local invocation, ADR-0013 D6), and the replay passed against 855b34e. The gates logged:
  • manifest: all checks passed;
  • fragments: cut consumed: changelog.d/1541-reusable-pr-gates.added.md (CHANGELOG.md modified), coverage and density PASS;
  • changelog_body: version=0.66.0 date=2026-10-05, all sections present;
  • register: file scan only, 0 hits (#1548);
  • ac_closure: nothing to check;
  • workflow_parse: PARSED=38 TOTAL=38.
    Then the tree was unchanged, and attest says every expected gate ran. pr / gates is success.
• The pr / <gate> and pr / split result rows read "Has been skipped": those are the split-layout jobs under combined, as expected.
• tests / bats (run 19847, job 0): 1..246, no not ok.
• tests / checks (job 1): attest 14 of 14.
• The old wrappers are all still green, as they stay until #1542: manifest-check, fragment-check (coverage, density), changelog-body-check, register-check, ac-closure-check and workflow-parse-check.

Next: Alex merges with the admin bypass. After the cut, check the v0.66.0 tag, its goreleaser assets and the minisign signature before tmux-tell's FETCH arm depends on them.

Verdict: APPROVE at 57c71b619ba89e2ca66d780c7df80076847fb5db Summary: the cut is clean and additive. v0.66.0 adds `reusable-pr-gates.yml` and removes nothing. The bake rewrites all 20 markers, the new reusable on both providers included, and the CHANGELOG carries exactly the one fragment. The `release-prep/` exemption from #1540 ran live for the first time and logged EXEMPT. Verified at source (AGENTS.md section 6). Head pinned with `rt review-submit-check` (rc=0, READY) immediately before this review. Base `855b34e` is still live main's tip. One commit, `57c71b6 chore(release): prepare v0.66.0`, by release-bot. ## 1. CHANGELOG and VERSION - **`VERSION`:** `0.65.0` becomes `0.66.0`. - **`## [v0.66.0] - 2026-10-05`:** Added holds exactly one bullet, the header line of `changelog.d/1541-reusable-pr-gates.added.md`. Changed, Fixed, Removed, Deprecated and Upgrade each read `None.` - **The fragment is deleted in this PR.** It was the only fragment on the base: main's `changelog.d/` held `.keep`, `.template.md` and that file. So no base fragment survives the cut (the #1305 shape), and the load-bearing `.keep` stays (AGENTS.md section 12). - **The fragment's body paragraph is not in CHANGELOG.md.** That matches existing behaviour: v0.65.0 (`c68b696`) also rendered only each fragment's header line, from fragments that carried bodies. It is not a defect of this cut. - **No removal:** nothing else is deleted, and no workflow file changes beyond its marker. ## 2. The bake: all 20 markers, the marker line the only change `git diff 855b34e...57c71b6` over `.forgejo/workflows` and `.gitea/workflows` gives exactly 20 removed and 20 added lines, all identical: ``` - BUILD_BAKED_TOOLKIT_REF: 'main' # release-toolkit-build-ref (auto-updated by rt prep / rt repin) + BUILD_BAKED_TOOLKIT_REF: 'v0.66.0' # release-toolkit-build-ref (auto-updated by rt prep / rt repin) ``` That covers 10 reusables on each provider: ac-closure, changelog-body, changelog-fragment, manifest, **pr-gates**, prepared-uncut, recover-pending-cut, register, release and workflow-parse. A grep over every workflow file at head finds no `release-toolkit-build-ref` marker with any value other than `'v0.66.0'`. So `reusable-pr-gates.yml@v0.66.0` carries its own version. A tag-pinned adopter's D6 resolve takes the "tag pin, baked tag" arm, not the #1222 fallback or the new refusal. `rt post-cut` resets main to `'main'` afterwards. ## 3. The `release-prep/` exemption (#1540), first live run `toolkit-self-gates` (run 19848, job 0, commit 57c71b619b), g10: ``` check-self-bootstrap: EXEMPT on the release-prep rolling PR (release-prep/rolling, #304). check-self-bootstrap: the merge fires push:main, where check-self-bootstrap.yml runs the full check. ``` Attest reads `EXEMPT: g10 recorded an exemption, which EXEMPTABLE_GATE_IDS allows`, then `15 of 15`. The other moved gates ran normally: - g11: twins match; - g12: `#1157 still refused`; - g13: `prep-order-check: PASS`; - g14: digest PASS. ## 4. CI, read in job logs (Axis C) All 32 statuses are success. - **`pr / plan, and run every gate when combined`** (run 19844, job 1): it resolved the toolkit ref to `main` (source=toolkit-self local invocation, ADR-0013 D6), and the replay passed against `855b34e`. The gates logged: - manifest: `all checks passed`; - fragments: `cut consumed: changelog.d/1541-reusable-pr-gates.added.md (CHANGELOG.md modified)`, coverage and density PASS; - changelog_body: `version=0.66.0 date=2026-10-05`, all sections present; - register: file scan only, 0 hits (#1548); - ac_closure: nothing to check; - workflow_parse: `PARSED=38 TOTAL=38`. Then the tree was unchanged, and attest says every expected gate ran. `pr / gates` is success. - **The `pr / <gate>` and `pr / split result` rows** read "Has been skipped": those are the split-layout jobs under `combined`, as expected. - **`tests / bats`** (run 19847, job 0): `1..246`, no `not ok`. - **`tests / checks`** (job 1): attest `14 of 14`. - **The old wrappers are all still green**, as they stay until #1542: manifest-check, fragment-check (coverage, density), changelog-body-check, register-check, ac-closure-check and workflow-parse-check. **Next:** Alex merges with the admin bypass. After the cut, check the `v0.66.0` tag, its goreleaser assets and the minisign signature before tmux-tell's FETCH arm depends on them.

alex approved these changes 2026-10-05 20:06:08 +02:00

alex merged commit 57c71b619b into main 2026-10-05 20:06:23 +02:00

alex deleted branch release-prep/rolling 2026-10-05 20:06:23 +02:00

forgejo-actions commented 2026-10-05 20:07:13 +02:00

• Copy link
• Copy Markdown

Landing identity record

• PR: #1549
• landed commit (server merge_commit_sha): 57c71b619ba89e2ca66d780c7df80076847fb5db
• effective official approval(s):
  • @alex, review #7239, stamped commit: 57c71b619ba89e2ca66d780c7df80076847fb5db
• replay comparison: no identity change (stamped SHA equals landed SHA)

This is a post-merge identity record. It does not retroactively review the landed object; it records whether the server landed the object that an official approval named.

<!-- release-toolkit:landing-review-record-v1 landed=57c71b619ba89e2ca66d780c7df80076847fb5db --> ## Landing identity record - PR: #1549 - landed commit (server merge_commit_sha): `57c71b619ba89e2ca66d780c7df80076847fb5db` - effective official approval(s): - @alex, review #7239, stamped commit: `57c71b619ba89e2ca66d780c7df80076847fb5db` - replay comparison: no identity change (stamped SHA equals landed SHA) This is a post-merge identity record. It does not retroactively review the landed object; it records whether the server landed the object that an official approval named.

Sign in to join this conversation.

Reviewers

No reviewers

surveyor

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

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

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

No description provided.