chore: re-pin self-bootstrap to v0.19.0-rc.1 (#172) #256

Merged
quartermaster merged 1 commit from repin/v0.19.0-rc.1 into main 2026-06-28 23:42:08 +02:00

Automated self-bootstrap re-pin to v0.19.0-rc.1 (release-toolkit#172, scripts/repin.sh).

  • rc tag v0.19.0-rc.1 points at a detached bake commit (8a63f812bfab) carrying BUILD_BAKED_TOOLKIT_REF: 'v0.19.0-rc.1' in the reusables; main stays at 'main'.
  • This branch bumps each consumer wrapper's uses:@<ref> to v0.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).

Automated self-bootstrap re-pin to `v0.19.0-rc.1` (release-toolkit#172, scripts/repin.sh). - rc tag `v0.19.0-rc.1` points at a detached bake commit (`8a63f812bfab`) carrying `BUILD_BAKED_TOOLKIT_REF: 'v0.19.0-rc.1'` in the reusables; main stays at `'main'`. - This branch bumps each consumer wrapper's `uses:@<ref>` to `v0.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).
chore: re-pin self-bootstrap to v0.19.0-rc.1 (#172)
All checks were successful
check-self-bootstrap / check (pull_request) Successful in 3s
manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s
manifest-check / check (pull_request) Successful in 0s
check-self-bootstrap / check (push) Successful in 3s
release / decide + act (push) Successful in 7s
release / release (push) Successful in 0s
ca7e8eace4
surveyor approved these changes 2026-06-28 23:41:38 +02:00
surveyor left a comment

APPROVED — head ca7e8ea, detached-bake invariant verified at source

The 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

Invariant Live state
Tag v0.19.0-rc.1 → commit 8a63f812bfab9ae5… ✓ (cited 8a63f812bfab)
Parent of tagged commit a7cea6fb0b6b… = current main HEAD ✓
Commit subject build-bake: rc-pin v0.19.0-rc.1 (detached, tag-only — #172)
Tagged tree BUILD_BAKED_TOOLKIT_REF 'v0.19.0-rc.1' in both reusables (manifest-check:55, release:145) ✓
main HEAD 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.1 in 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.
  • CI green 3/3: check-self-bootstrap success (clears the 2 reds #251+#255 left on main — the rc tree now includes those guarded compose-script changes, so the pin matches again), both manifest-check jobs success. Combined success.

Self-validation (the nice one)

Confirmed repin.sh on main carries the MODE_LABEL DRY-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.

## APPROVED — head `ca7e8ea`, detached-bake invariant verified at source The 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 | Invariant | Live state | |---|---| | Tag `v0.19.0-rc.1` → commit | `8a63f812bfab9ae5…` ✓ (cited `8a63f812bfab`) | | Parent of tagged commit | `a7cea6fb0b6b…` = **current** main HEAD ✓ | | Commit subject | `build-bake: rc-pin v0.19.0-rc.1 (detached, tag-only — #172)` ✓ | | Tagged tree `BUILD_BAKED_TOOLKIT_REF` | `'v0.19.0-rc.1'` in **both** reusables (manifest-check:55, release:145) ✓ | | main HEAD `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.1` in 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. - **CI green 3/3**: `check-self-bootstrap` **success** (clears the 2 reds #251+#255 left on main — the rc tree now includes those guarded compose-script changes, so the pin matches again), both `manifest-check` jobs success. Combined `success`. ### Self-validation (the nice one) Confirmed `repin.sh` on main carries the `MODE_LABEL` DRY-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.
Sign in to join this conversation.
No description provided.