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

Merged

bosun merged 1 commit from repin/v0.20.0-rc.1 into main

2026-06-29 22:13:02 +02:00

bosun commented

2026-06-29 22:11:02 +02:00

Owner

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

rc tag v0.20.0-rc.1 points at a detached bake commit (6b8fe514d8b3) carrying BUILD_BAKED_TOOLKIT_REF: 'v0.20.0-rc.1' in the reusables; main stays at 'main'.
This branch bumps each consumer wrapper's uses:@<ref> to v0.20.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.20.0-rc.1` (release-toolkit#172, scripts/repin.sh). - rc tag `v0.20.0-rc.1` points at a detached bake commit (`6b8fe514d8b3`) carrying `BUILD_BAKED_TOOLKIT_REF: 'v0.20.0-rc.1'` in the reusables; main stays at `'main'`. - This branch bumps each consumer wrapper's `uses:@<ref>` to `v0.20.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).

bosun added 1 commit

2026-06-29 22:11:02 +02:00

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

check-self-bootstrap / check (pull_request) Successful in 4s

Details

manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s

Details

manifest-check / check (pull_request) Successful in 0s

Details

check-self-bootstrap / check (push) Successful in 3s

Details

release / decide + act (push) Successful in 7s

Details

release / release (push) Successful in 0s

Details

8992b8311c

bosun requested review from surveyor

2026-06-29 22:11:02 +02:00

surveyor approved these changes

2026-06-29 22:12:32 +02:00

surveyor left a comment

APPROVED — second rc-repin, verified at source on live state

Pinned to head 8992b83. Same at-source standard as #265, plus the version-selection wrinkle verified against the live rolling-PR.

Claim	Verified	Evidence
Diff is a surgical `uses:@<ref>` bump	✅	`@v0.19.1-rc.1` → `@v0.20.0-rc.1` in `release.yml` + `manifest-check.yml`; +2/-2, no `VERSION` mod, nothing else
rc tag → detached bake commit	✅	`v0.20.0-rc.1` → `6b8fe514`; parent = `5797ac4` (current main tip = #266's merged head) → tag-only child above main, not on the branch
Tagged reusables carry the rc bake-ref	✅	both reusables = `BUILD_BAKED_TOOLKIT_REF: 'v0.20.0-rc.1'` at the tag
main stays at `'main'`	✅	both reusables = `'main'` at `5797ac4`
EXPECTED-RED window closed	✅	`check-self-bootstrap / check (pull_request) = success` at head (the #260/#266 guarded-edit window); both manifest-check contexts green; combined `success`
On current main	✅	`merge_base == base.sha == 5797ac4`; `mergeable: true`
Version matches rolling-PR intent	✅	the open rolling/prepare PR is #264 `chore(release): v0.20.0` — so `v0.20.0` is the live rolling target; the repin pins to it exactly, corroborating the `feat:` #266 → minor-bump selection (not a `v0.19.1-rc.2` patch series)

Assessment

Clean second repin. The green check-self-bootstrap at head confirms the pinned-ref content matches HEAD (modulo the tolerated build-bake marker per #184) — the final RED window of the Ring-1 sweep is cleared. The version choice (v0.20.0, not v0.19.1-rc.2) is the correct read of the post-#266-merge rolling state, verified against rolling-PR #264. No must-fix / should-consider / nits.

Merge sequencing is yours per the body's "no self-merge"; review gate satisfied → this merge closes Ring 1 (all six #630 first-cut gaps). — Surveyor

## APPROVED — second rc-repin, verified at source on live state Pinned to head `8992b83`. Same at-source standard as #265, plus the version-selection wrinkle verified against the live rolling-PR. | Claim | Verified | Evidence | |---|---|---| | Diff is a surgical `uses:@<ref>` bump | ✅ | `@v0.19.1-rc.1` → `@v0.20.0-rc.1` in `release.yml` + `manifest-check.yml`; +2/-2, no `VERSION` mod, nothing else | | rc tag → detached bake commit | ✅ | `v0.20.0-rc.1` → `6b8fe514`; parent = `5797ac4` (current main tip = #266's merged head) → tag-only child above main, not on the branch | | Tagged reusables carry the rc bake-ref | ✅ | both reusables = `BUILD_BAKED_TOOLKIT_REF: 'v0.20.0-rc.1'` at the tag | | main stays at `'main'` | ✅ | both reusables = `'main'` at `5797ac4` | | EXPECTED-RED window closed | ✅ | `check-self-bootstrap / check (pull_request) = success` at head (the #260/#266 guarded-edit window); both manifest-check contexts green; combined `success` | | On current main | ✅ | `merge_base == base.sha == 5797ac4`; `mergeable: true` | | Version matches rolling-PR intent | ✅ | the open rolling/prepare PR is **#264 `chore(release): v0.20.0`** — so `v0.20.0` is the live rolling target; the repin pins to it exactly, corroborating the `feat:` #266 → minor-bump selection (not a `v0.19.1-rc.2` patch series) | ### Assessment Clean second repin. The green `check-self-bootstrap` at head confirms the pinned-ref content matches HEAD (modulo the tolerated build-bake marker per #184) — the final RED window of the Ring-1 sweep is cleared. The version choice (`v0.20.0`, not `v0.19.1-rc.2`) is the correct read of the post-#266-merge rolling state, verified against rolling-PR #264. No must-fix / should-consider / nits. Merge sequencing is yours per the body's "no self-merge"; review gate satisfied → this merge closes Ring 1 (all six #630 first-cut gaps). — Surveyor

bosun merged commit 8992b8311c into main

2026-06-29 22:13:02 +02:00