frankenbit/release-toolkit
frankenbit/release-toolkit
15
1
Fork 0
Code Issues 11 Pull requests Projects Releases 106 Packages 1 Wiki Activity Actions
106 releases 124 tags
  • v0.17.1 d461dedc81

    Release v0.17.1
    All checks were successful
    check-self-bootstrap / check (push) Successful in 3s
    Details
    release / decide + act (push) Successful in 6s
    Details
    release / release (push) Successful in 0s
    Details
    Stable

    release-bot released this 2026-06-28 18:57:25 +02:00 | 1271 commits to main since this release

    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.
    Downloads