chore(release): v0.45.1 #874
No reviewers
Labels
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!874
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release-prep/rolling"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changelog density — clean
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
mainon every compose.Added
None.
Changed
None.
Fixed
None.
Removed
None.
Deprecated
None.
Upgrade
None.
Internal
CI gates now consume measured standard runner images — missing bats, shellcheck, jq, or Graphviz fails loud instead of triggering runtime package installation (#863)
Release cuts now publish the digest-pinned action from the measured Docker-capable runner and hand the tagged action artifact to verification (#872)
bb17604890de927aad62Reviewed exact head
de927aad62(parentbd643d639c) and APPROVED.The composed cut is coherent: CHANGELOG v0.45.1 dated 2026-08-25 has both source fragments (#863 and #872) verbatim under Internal, with both fragments consumed; VERSION and the prior-release manifest anchor remain consistent. Re-running
rt prep --target-version 0.45.1 --dry-runfrom the exact parent reproduced the PR tree byte-for-byte across all changed paths.Pin/cut checks passed: all five BUILD_BAKED_TOOLKIT_REF markers are v0.45.1; all 13 consumer-side reusable pins are v0.45.1 while the toolkit-self release wrapper remains @main; no stale v0.45.0 pin remains outside the previous-release manifest/history; action.yml's digest marker is unchanged for the cut-time handoff.
rt compose-verify --version 0.45.1, changelog-body-check, fragment-check, register-check, manifest-check, check-self-bootstrap, and all workflow YAML parsing pass. The release dry-run emits the expected v0.45.1 tag and composed release body.Independent gates pass: go build ./..., go vet ./..., go test -count=1 ./..., 54 Bats arms, and shellcheck. Forgejo at final read reports mergeable=true, exact head-bound state, and 14/14 contexts successful (the expected skipped bootstrap context included). No findings.
Reviewed exact head
de927aad62(parentbd643d639c) and APPROVED.The composed cut is coherent: CHANGELOG v0.45.1 dated 2026-08-25 has both source fragments (#863 and #872) verbatim under Internal, with both fragments consumed; VERSION and the prior-release manifest anchor remain consistent. Re-running
rt prep --target-version 0.45.1 --dry-runfrom the exact parent reproduced the PR tree byte-for-byte across all changed paths.Pin/cut checks passed: all five BUILD_BAKED_TOOLKIT_REF markers are v0.45.1; all 13 consumer-side reusable pins are v0.45.1 while the toolkit-self release wrapper remains @main; no stale v0.45.0 pin remains outside the previous-release manifest/history; action.yml's digest marker is unchanged for the cut-time handoff.
rt compose-verify --version 0.45.1, changelog-body-check, fragment-check, register-check, manifest-check, check-self-bootstrap, and all workflow YAML parsing pass. The release dry-run emits the expected v0.45.1 tag and composed release body.Independent gates pass: go build ./..., go vet ./..., go test -count=1 ./..., 54 Bats arms, and shellcheck. Forgejo at final read reports mergeable=true, exact head-bound state, and 14/14 contexts successful (the expected skipped bootstrap context included). No findings.