chore: re-pin self-bootstrap to v0.28.0-rc.1 (#172) #415
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!415
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "repin/v0.28.0-rc.1"
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?
Automated self-bootstrap re-pin to
v0.28.0-rc.1(release-toolkit#172, scripts/repin.sh).v0.28.0-rc.1points at a detached bake commit (eda6b6ae0cf8) carryingBUILD_BAKED_TOOLKIT_REF: 'v0.28.0-rc.1'in the reusables; main stays at'main'.uses:@<ref>tov0.28.0-rc.1.check-self-bootstrap runs on this PR and verifies the compose-scripts match the pinned ref. Merge after review (no self-merge).
APPROVED — clean re-pin, completeness verified
Same verification as #405 (simple bumps are where things slip):
@v0.27.0-rc.1 → @v0.28.0-rc.1on thejobs.*.uses:line; no#comment line touched, so#410's
@vX.Y.Zdocstring placeholders stay put.uses:refs now at@v0.28.0-rc.1, zerostale.
register-check.ymlamong them (dogfooding continues; #395's bake-listregistration still driving the sweep).
feedback_repin_sequence(the rc tag baked live @HEAD of the right base this time).
Clear to self-merge → check-self-bootstrap green → #408 v1.0.0-frozen.