chore(release): v0.17.1 #243

Merged

quartermaster merged 1 commit from release-prep/rolling into main

2026-06-28 18:57:16 +02:00

release-bot commented

2026-06-28 18:54:04 +02:00

Member

Fixed

The Layer 2 / Layer 3 cut-safeguard now finds the merged cut PR via Forgejo's direct commit->PR lookup (GET /repos/{owner}/{repo}/commits/{sha}/pull) instead of a pulls?state=closed&sort=updated&limit=5 list-and-filter. The old query paired an arbitrary 5-PR window with Forgejo's issue_id-descending sort=updated ordering, so a rolling cut PR created early but merged late could fall outside the window once more than a few PRs closed between cuts -- the safeguard then returned empty and the cut fell through to mode=update. (Anchor: the v0.17.0 cut, where rolling PR #227 sat at list position 11 of the limit=5 query and had to be recovered manually.) The direct lookup keys on the merged commit server-side and has no window to outgrow; a 404 (no PR for the commit, including the brief post-merge indexing-lag window) collapses to the existing empty-result contract that the caller's retry + protective fall-through already handle.

release-decide: Layer 2 cut-safeguard uses direct commit->PR lookup (#240)

### Fixed The Layer 2 / Layer 3 cut-safeguard now finds the merged cut PR via Forgejo's direct commit->PR lookup (`GET /repos/{owner}/{repo}/commits/{sha}/pull`) instead of a `pulls?state=closed&sort=updated&limit=5` list-and-filter. The old query paired an arbitrary 5-PR window with Forgejo's `issue_id`-descending `sort=updated` ordering, so a rolling cut PR created early but merged late could fall outside the window once more than a few PRs closed between cuts -- the safeguard then returned empty and the cut fell through to `mode=update`. (Anchor: the v0.17.0 cut, where rolling PR #227 sat at list position 11 of the limit=5 query and had to be recovered manually.) The direct lookup keys on the merged commit server-side and has no window to outgrow; a 404 (no PR for the commit, including the brief post-merge indexing-lag window) collapses to the existing empty-result contract that the caller's retry + protective fall-through already handle. - **release-decide**: Layer 2 cut-safeguard uses direct commit->PR lookup (#240)

forgejo-actions force-pushed release-prep/rolling from efee99685f

check-self-bootstrap / check (pull_request) Failing after 3s

Details

manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s

Details

manifest-check / check (pull_request) Successful in 0s

Details

to d461dedc81

check-self-bootstrap / check (push) Successful in 3s

Details

release / decide + act (push) Successful in 6s

Details

release / release (push) Successful in 0s

Details

2026-06-28 18:56:41 +02:00

Compare

quartermaster approved these changes

2026-06-28 18:57:12 +02:00

quartermaster left a comment

Standing-approval covers the cut PR. Auto-generated prep for v0.17.1 = #240 Layer 2 substrate fix (#241 merged at eaa0f50). Patch bump per #240's fix: classification.

Standing-approval covers the cut PR. Auto-generated prep for v0.17.1 = #240 Layer 2 substrate fix (#241 merged at eaa0f50). Patch bump per #240's `fix:` classification.

quartermaster merged commit d461dedc81 into main

2026-06-28 18:57:16 +02:00