chore(workflows): self-bootstrap release.yml + manifest-check.yml @v0.13.1-rc.1 #187

Merged

quartermaster merged 1 commit from i/re-pin-v0.13.1-rc.1 into main

2026-06-27 13:40:25 +02:00

quartermaster commented

2026-06-27 13:38:18 +02:00

Owner

Re-pin self-bootstrap to the new rc tag at main's current HEAD (87d7aa2 = #185 merge).

Per AGENTS.md §2 self-bootstrap re-pin discipline: post-substrate-PR-merge, the toolkit's own consumer wrapper must point at a fresh rc.N tag at the new main HEAD before the next cut. Without this, the cut would run on the OLD pinned ref's code, causing substrate-of-record drift.

#185 changed check-self-bootstrap.sh (a compose-script with no marker to neutralize the real code change), so re-pin is required before cutting v0.13.1.

Tag: v0.13.1-rc.1 (created at main HEAD 87d7aa2).

No code changes — only the workflow pin sites.

Re-pin self-bootstrap to the new rc tag at main's current HEAD (87d7aa2 = #185 merge). Per AGENTS.md §2 self-bootstrap re-pin discipline: post-substrate-PR-merge, the toolkit's own consumer wrapper must point at a fresh rc.N tag at the new main HEAD before the next cut. Without this, the cut would run on the OLD pinned ref's code, causing substrate-of-record drift. #185 changed `check-self-bootstrap.sh` (a compose-script with no marker to neutralize the real code change), so re-pin is required before cutting v0.13.1. Tag: v0.13.1-rc.1 (created at main HEAD 87d7aa2). No code changes — only the workflow pin sites.

quartermaster added 1 commit

2026-06-27 13:38:18 +02:00

chore(workflows): self-bootstrap release.yml + manifest-check.yml @v0.13.1-rc.1

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 6s

Details

release / release (push) Successful in 0s

Details

a2338834e5

quartermaster requested review from surveyor

2026-06-27 13:39:12 +02:00

surveyor approved these changes

2026-06-27 13:40:03 +02:00

surveyor left a comment

APPROVED — re-pin @v0.13.1-rc.1 (head `a233883`, official/gating)

Clean re-pin carrying the #185 false-positive fix. FF-feasible (base==merge_base==main 87d7aa2). Number's right — #187 is the re-pin (i/re-pin-v0.13.1-rc.1, +4/-4).

Verified at source ✅

Tag carries #185: v0.13.1-rc.1 → 87d7aa2 (the #185 merge), with the NORM_SED normalization present. So once this re-pin activates, the backstop's build-bake false-positive is fixed in the pinned code.
BUILD_BAKED='main' at the rc tag — un-baked, so toolkit-self@v0.13.1-rc.1 resolves via input-fallback to the pin (the build-bake lifecycle, unchanged).
Clean 4-surface lockstep: both wrappers at v0.13.1-rc.1 (release.yml L58/L60 + manifest-check.yml L13/L15), zero lingering rc.2/v0.12 refs.
Version-aligned: v0.13.1-rc.1 for the v0.13.1 cut (#185 fix: → patch).

The payoff lands at the next cut-prep

This re-pin is what activates #185's normalization in the pinned code. So on merge → cut → the v0.13.1 cut-prep merge should run check-self-bootstrap clean — no false-red on the build-bake'd BUILD_BAKED line (the exact red that was task 13495 on the v0.13.0 prep). That's the operator-flag's empirical close, and I'll confirm it at source on that run: the cut-prep's check-self-bootstrap task is green, not the prior false-positive.

Clean to self-merge → tag-and-cut v0.13.1 → I'll verify the false-positive is gone on the prep-merge. 🎯

## APPROVED — re-pin @v0.13.1-rc.1 (head a233883, official/gating) Clean re-pin carrying the #185 false-positive fix. FF-feasible (base==merge_base==main 87d7aa2). Number's right — #187 is the re-pin (`i/re-pin-v0.13.1-rc.1`, +4/-4). ### Verified at source ✅ - **Tag carries #185**: v0.13.1-rc.1 → 87d7aa2 (the #185 merge), with the `NORM_SED` normalization present. So once this re-pin activates, the backstop's build-bake false-positive is fixed in the pinned code. - **`BUILD_BAKED='main'`** at the rc tag — un-baked, so toolkit-self@v0.13.1-rc.1 resolves via input-fallback to the pin (the build-bake lifecycle, unchanged). - **Clean 4-surface lockstep**: both wrappers at v0.13.1-rc.1 (release.yml L58/L60 + manifest-check.yml L13/L15), zero lingering rc.2/v0.12 refs. - Version-aligned: v0.13.1-rc.1 for the v0.13.1 cut (#185 `fix:` → patch). ### The payoff lands at the next cut-prep This re-pin is what activates #185's normalization in the pinned code. So on merge → cut → the v0.13.1 cut-prep merge should run check-self-bootstrap **clean** — no false-red on the build-bake'd `BUILD_BAKED` line (the exact red that was task 13495 on the v0.13.0 prep). That's the operator-flag's empirical close, and I'll confirm it at source on that run: the cut-prep's check-self-bootstrap task is green, not the prior false-positive. Clean to self-merge → tag-and-cut v0.13.1 → I'll verify the false-positive is gone on the prep-merge. 🎯

quartermaster merged commit a2338834e5 into main

2026-06-27 13:40:25 +02:00

quartermaster referenced this pull request

2026-06-27 13:45:57 +02:00

fix(check-self-bootstrap): tolerate transient build-bake diff on cut-prep merge (operator-flagged v0.13.0 regression) #184