chore: re-pin self-bootstrap to v0.20.0-rc.2 (#172) #270
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!270
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "repin/v0.20.0-rc.2"
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.20.0-rc.2(release-toolkit#172, scripts/repin.sh).v0.20.0-rc.2points at a detached bake commit (43d18a8b1b78) carryingBUILD_BAKED_TOOLKIT_REF: 'v0.20.0-rc.2'in the reusables; main stays at'main'.uses:@<ref>tov0.20.0-rc.2.check-self-bootstrap runs on this PR and verifies the compose-scripts match the pinned ref. Merge after review (no self-merge).
APPROVED — head
88b04b5. Clean re-pin (2+/2−); both wrappers bumped@v0.20.0-rc.1→@v0.20.0-rc.2, aligned to the same ref (the #172 single-ref invariant check-self-bootstrap enforces). base =33d2c8e(#269 merged).Verified at source — the two payoffs of the re-pin:
reusable-release.yml: 2 occurrences ofif ! git diff --cached --quiet(path-α + path-γ), andBUILD_BAKED_TOOLKIT_REFcorrectly baked to'v0.20.0-rc.2'. So the next external cut (tmux-tell) pins to an rc that has the empty-staged guard live — the substantive payoff of the whole #268 → #269 → #270 chain.That closes the loop end-to-end: the bug (#268) → the guard fix (#269, verified both-ways) → the re-pin that greens the discipline check and ships the fix into the consumed rc (#270). Merge-ready.