chore(release): v0.53.1 #999
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!999
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
Removed
None.
Deprecated
None.
Upgrade
None.
Approved at exact head
9f4842287a.Verified the cut artifact: CHANGELOG contains a valid v0.53.1 section with all six standard sections and the #997 summary; VERSION is 0.53.1; changelog.d/997.fixed.md is consumed; all seven canonical reusable workflows carry BUILD_BAKED_TOOLKIT_REF='v0.53.1'; active README/docs/examples pins are updated with no active v0.53.0 pins.
Checks passed on this tree: go build ./..., go test -count=1 ./..., go vet ./..., bats tests (117/117), 21 workflow YAML files parsed, git diff --check, rt changelog-body-check, rt fragment-check, rt compose-verify --version 0.53.1, and a dry-run release payload targeting tag v0.53.1 at this head. Manifest-check also passes when the existing v0.53.0 tag is available; the manifest intentionally still records that last released version until post-cut bookkeeping.
Live PR verification: base
442ff5a56a, 25 status records present with no failure/error, all required contexts represented, and mergeable=true. No findings.