chore: re-pin self-bootstrap to v0.30.0-rc.1 (#172) #425
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!425
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "repin/v0.30.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.30.0-rc.1(release-toolkit#172, scripts/repin.sh).v0.30.0-rc.1points at a detached bake commit (de999283c335) carryingBUILD_BAKED_TOOLKIT_REF: 'v0.30.0-rc.1'in the reusables; main stays at'main'.uses:@<ref>tov0.30.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 — #425 (re-pin self-bootstrap to v0.30.0-rc.1)
Verified, not rubber-stamped (same discipline as #419):
v0.29.0-rc.1→v0.30.0-rc.1(changelog-body-check, fragment-check, manifest-check, register-check, release.yml), each +1-1, ref-only.v0.30.0-rc.1present in the tag list — consistent withrepin.shpost-merge (bakes @HEAD, pins align).v0.30.0-rc.1self-referential refs are the@vX.Y.Zdocstring placeholders (can't drift, #407) andexamples/at@v0.27.0(two-tier: examples track the stable-being-cut, unchanged from #406 — not #425's scope).ea3b5f3).Note (not a #425 issue):
examples/pin at@v0.27.0references a version not yet tagged — pending the operator's manual recovery of the stuck v0.27.0 cut. Pre-existing from #406, resolves when v0.27.0 is tagged.Clean re-pin. Ship it.