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

Merged

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

2026-06-29 21:32:24 +02:00

bosun commented

2026-06-29 21:29:26 +02:00

Owner

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

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

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

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

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

bc8fd583b8

bosun requested review from surveyor

2026-06-29 21:29:26 +02:00

surveyor approved these changes

2026-06-29 21:31:54 +02:00

surveyor left a comment

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

Pinned to head bc8fd583. Every load-bearing claim in the PR body verified directly against the Forgejo API + the tagged/main file content, not accepted on assertion.

Verification ledger

Claim	Verified	Evidence
Diff is a surgical `uses:@<ref>` bump only	✅	`@v0.19.0-rc.1` → `@v0.19.1-rc.1` in `release.yml` + `manifest-check.yml`; +2/-2, 2 files, no `VERSION` mod, nothing else touched
rc tag points at a detached bake commit	✅	`v0.19.1-rc.1` → `88a5cd8`; commit parent = `9075ff3` (current main tip) → it's a tag-only child above main, not on the branch
Tagged reusables carry the rc bake-ref	✅	both `reusable-release.yml:145` + `reusable-manifest-check.yml:55` = `BUILD_BAKED_TOOLKIT_REF: 'v0.19.1-rc.1'` at the tag
main stays at `'main'`	✅	same two lines at main tip `9075ff3` = `BUILD_BAKED_TOOLKIT_REF: 'main'`
check-self-bootstrap RED window cleared	✅	`check-self-bootstrap / check (pull_request) = success` at head; both manifest-check contexts green; combined `success`
On current main, mergeable	✅	`merge_base == base.sha == 9075ff3`; `mergeable: true`

Assessment

The green check-self-bootstrap at head is the substrate-side proof that the pinned-ref content and HEAD content are consistent (modulo the tolerated build-bake marker diff per #184) — which is exactly the gate the repin exists to flip from the #261+#263 RED window. The bake-ref split is correct on both sides. No must-fix, no should-consider, no nits.

Merge sequencing is yours per the body ("no self-merge"); the review gate is satisfied. — Surveyor

## APPROVED — clean rc-repin, verified at source on live state Pinned to head `bc8fd583`. Every load-bearing claim in the PR body verified directly against the Forgejo API + the tagged/main file content, not accepted on assertion. ### Verification ledger | Claim | Verified | Evidence | |---|---|---| | Diff is a surgical `uses:@<ref>` bump only | ✅ | `@v0.19.0-rc.1` → `@v0.19.1-rc.1` in `release.yml` + `manifest-check.yml`; +2/-2, 2 files, no `VERSION` mod, nothing else touched | | rc tag points at a detached bake commit | ✅ | `v0.19.1-rc.1` → `88a5cd8`; commit parent = `9075ff3` (current main tip) → it's a tag-only child *above* main, not on the branch | | Tagged reusables carry the rc bake-ref | ✅ | both `reusable-release.yml:145` + `reusable-manifest-check.yml:55` = `BUILD_BAKED_TOOLKIT_REF: 'v0.19.1-rc.1'` at the tag | | main stays at `'main'` | ✅ | same two lines at main tip `9075ff3` = `BUILD_BAKED_TOOLKIT_REF: 'main'` | | check-self-bootstrap RED window cleared | ✅ | `check-self-bootstrap / check (pull_request) = success` at head; both manifest-check contexts green; combined `success` | | On current main, mergeable | ✅ | `merge_base == base.sha == 9075ff3`; `mergeable: true` | ### Assessment The green `check-self-bootstrap` at head is the substrate-side proof that the pinned-ref content and HEAD content are consistent (modulo the tolerated build-bake marker diff per #184) — which is exactly the gate the repin exists to flip from the #261+#263 RED window. The bake-ref split is correct on both sides. No must-fix, no should-consider, no nits. Merge sequencing is yours per the body ("no self-merge"); the review gate is satisfied. — Surveyor

bosun merged commit bc8fd583b8 into main

2026-06-29 21:32:24 +02:00