chore: re-pin self-bootstrap to v0.19.0-rc.1 (#172) #256
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!256
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "repin/v0.19.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.19.0-rc.1(release-toolkit#172, scripts/repin.sh).v0.19.0-rc.1points at a detached bake commit (8a63f812bfab) carryingBUILD_BAKED_TOOLKIT_REF: 'v0.19.0-rc.1'in the reusables; main stays at'main'.uses:@<ref>tov0.19.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 — head
ca7e8ea, detached-bake invariant verified at sourceThe reviewable diff is the +2/-2 wrapper bump, but the load-bearing claim is the #172 detached-bake structure the tag points at — verified that directly against the live git objects, not the dispatch citation. Every claim matches.
Detached-bake invariant (#172) — verified
v0.19.0-rc.1→ commit8a63f812bfab9ae5…✓ (cited8a63f812bfab)a7cea6fb0b6b…= current main HEAD ✓build-bake: rc-pin v0.19.0-rc.1 (detached, tag-only — #172)✓BUILD_BAKED_TOOLKIT_REF'v0.19.0-rc.1'in both reusables (manifest-check:55, release:145) ✓BUILD_BAKED_TOOLKIT_REF'main'in both reusables — single-source-of-truth uncontaminated ✓The detached commit hangs off current main HEAD (not a stale base), carries the rc ref tag-only, and main stays
'main'. Clean.Wrapper bump + mergeability
@v0.18.0-rc.1→@v0.19.0-rc.1in both consumer wrappers (manifest-check.yml, release.yml). +2/-2, matches the tag's ref exactly.merge_base == base.sha == a7cea6fb= current post-#255 main → genuine FF, not behind-main.check-self-bootstrapsuccess (clears the 2 reds #251+#255 left on main — the rc tree now includes those guarded compose-script changes, so the pin matches again), bothmanifest-checkjobs success. Combinedsuccess.Self-validation (the nice one)
Confirmed
repin.shon main carries theMODE_LABELDRY-RUN/LIVE labeling (lines 61/63) — the #247 structural fix I proposed, now the tool that produced this PR. So the "LIVE: prefix throughout the output" you saw is the fix self-validating in production, exactly as intended. n=1 empirical confirmation that #247→#248 landed correctly.FYI (not a concern)
The resident wrapper pin was
v0.18.0-rc.1— i.e. the self-bootstrap pin tracks rc-cuts-of-minors, and v0.18.1 (patch) didn't re-pin the wrappers, which is why main carried the check-self-bootstrap reds since #251 until now. That's the disclosed #155/#251 discipline working as designed, not drift; flagging only so the rc-pin-cadence is on the record.5th post-Phase-2 re-pin, invariant held every time. Approved for your merge gate — FF-able as-is.