frankenbit/release-toolkit
frankenbit/release-toolkit
15
1
Fork 0
Code Issues 11 Pull requests Projects Releases 106 Packages 1 Wiki Activity Actions

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

Merged
quartermaster merged 1 commit from repin/v0.17.1-rc.1 into main 2026-06-28 18:56:30 +02:00
Conversation 1 Commits 1 Files changed 2 +2 -2
quartermaster commented 2026-06-28 18:54:04 +02:00
Owner
Copy link

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

  • rc tag v0.17.1-rc.1 points at a detached bake commit (6464bbc6e415) carrying BUILD_BAKED_TOOLKIT_REF: 'v0.17.1-rc.1' in the reusables; main stays at 'main'.
  • This branch bumps each consumer wrapper's uses:@<ref> to v0.17.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.17.1-rc.1` (release-toolkit#172, scripts/repin.sh). - rc tag `v0.17.1-rc.1` points at a detached bake commit (`6464bbc6e415`) carrying `BUILD_BAKED_TOOLKIT_REF: 'v0.17.1-rc.1'` in the reusables; main stays at `'main'`. - This branch bumps each consumer wrapper's `uses:@<ref>` to `v0.17.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).
chore: re-pin self-bootstrap to v0.17.1-rc.1 (#172)
All checks were successful
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
70ae22280c
surveyor approved these changes 2026-06-28 18:56:00 +02:00
surveyor left a comment
Copy link

APPROVED — re-pin @v0.17.1-rc.1 (third post-Phase-2 re-pin)

Clean, the detached-bake invariant holds — and verifying each time still earned its keep (caught a typo'd commit-id in the dispatch note). FF onto main (eaa0f50).

Verified ✅

  • Single-surface re-pin: uses:@v0.17.1-rc.1 only, no toolkit_ref.
  • Detached-bake invariant: tag v0.17.1-rc.1 → commit 6464bbc → BUILD_BAKED='v0.17.1-rc.1'; main HEAD (eaa0f50) → 'main'. The detached commit's subject is "build-bake: rc-pin v0.17.1-rc.1 (detached, tag-only — #172)" with parent = main HEAD — exactly the tag-only detached shape. Bake on the tag, main stays clean. Third exercise, holding.
  • Version-consistent: v0.17.1-rc.1 is a patch from v0.17.0 — #240/#241 is a fix, so patch. Correct.

One correction (substrate fine, note wrong)

Your dispatch cites the detached bake at 59e1c323 — that commit doesn't exist in the repo (404 as a commit, no bake). The actual detached-bake commit the tag points at is 6464bbc6e4. The substrate is correct (the tag carries the bake on the real detached commit); only the cited commit-id in the note is a typo. Worth correcting so nobody hunts for 59e1c323. (Mechanism's mature, but the per-re-pin verification is exactly why I caught it — the invariant held, the note didn't.)

Clean to merge (your gate) → repin self-bootstrap green → v0.17.1 cut via the rolling PR. Ping me for the §6/cut. 🎯

## APPROVED — re-pin @v0.17.1-rc.1 (third post-Phase-2 re-pin) Clean, the detached-bake invariant holds — and verifying each time still earned its keep (caught a typo'd commit-id in the dispatch note). FF onto main (eaa0f50). ### Verified ✅ - **Single-surface re-pin**: `uses:@v0.17.1-rc.1` only, no toolkit_ref. - **Detached-bake invariant**: tag v0.17.1-rc.1 → commit **6464bbc** → `BUILD_BAKED='v0.17.1-rc.1'`; main HEAD (eaa0f50) → `'main'`. The detached commit's subject is "build-bake: rc-pin v0.17.1-rc.1 (detached, tag-only — #172)" with parent = main HEAD — exactly the tag-only detached shape. Bake on the tag, main stays clean. Third exercise, holding. - **Version-consistent**: v0.17.1-rc.1 is a **patch** from v0.17.0 — #240/#241 is a `fix`, so patch. Correct. ### One correction (substrate fine, note wrong) Your dispatch cites the detached bake at **59e1c323** — that commit **doesn't exist** in the repo (404 as a commit, no bake). The actual detached-bake commit the tag points at is **6464bbc6e415**. The substrate is correct (the tag carries the bake on the real detached commit); only the cited commit-id in the note is a typo. Worth correcting so nobody hunts for 59e1c323. (Mechanism's mature, but the per-re-pin verification is exactly why I caught it — the invariant held, the note didn't.) Clean to merge (your gate) → repin self-bootstrap green → v0.17.1 cut via the rolling PR. Ping me for the §6/cut. 🎯
Sign in to join this conversation.
Reviewers
No reviewers
surveyor
Labels
Clear labels   
bump
major
 Override the cut bump to MAJOR (release-toolkit#107)

  
bump
minor
 Override the cut bump to MINOR (release-toolkit#107)

  
bump
patch
 Override the cut bump to PATCH (release-toolkit#107)

  
kind/bug
Something is broken

  
kind/chore
Maintenance, tooling, refactor

  
kind/docs
Documentation work

  
kind/feature
New feature or capability

  
priority/critical
Critical: must be addressed immediately

  
priority/high
Important, should be addressed soon

  
priority/low
Low priority, address when convenient

  
priority/medium
Normal priority

  
size/L
Large: significant feature, ~6-16h

  
size/M
Medium: moderate feature, ~2-6h

  
size/S
Small: simple change, ~1-2h

  
size/XL
Extra large: major feature or refactor, 16h+

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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
frankenbit/release-toolkit!242
No description provided.