No reviewers
Labels
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "i/self-bootstrap-v0.5.0-rc.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Self-bootstrap toolkit to dogfood its own #77 + #78 in the v0.5.0 cut
Verify-at-source on rolling PR #80 (just retargeted v0.4.1 → v0.5.0 per Surveyor c3f4's update-path force-reset prediction) caught: the workflow ran release-prep.sh @v0.4.0-rc.3 which doesn't have #77's frontmatter-stripping logic. Result:
---\nsummary: ...\n---block).release-toolkit-release-notes.mdsidecar generatedSame chicken-and-egg shape as v0.4.0's rc.2/rc.3 cycles — the toolkit must self-bootstrap to a new ref to dogfood substrate-changes that release-prep.sh itself implements.
What this PR does
Re-pins toolkit's
release.ymlfrom@v0.4.0-rc.3→@v0.5.0-rc.1(retagged at7876a10— current main, includes #77 + #78 + their folds).Pure 2-line ref bump. Same shape as PR #72 (rc.2 re-pin after #70) + PR #75 (rc.3 re-pin after #73).
Expected post-merge behavior
When this merges → push:main fires the workflow →
_release.yml@v0.5.0-rc.1runs:release-decide.shwalksv0.4.0..HEAD→ finds feat() #77 + fix() #78 + chore() commits →bump_max(minor, patch) = minor→next_version=0.5.0mode=update→release-prep.sh --rolling-mode --target-version 0.5.0(NOW with frontmatter-stripping + sidecar generation).release-toolkit-release-notes.mdsidecar present with short summaries grouped by kindCarry-forward observation worth banking (slice 5)
Banking: every major-version (v0.X.0) cut needs a self-bootstrap step when the cut includes substrate-changes to release-prep.sh OR draft-release.sh OR _release.yml itself. Pattern:
rc.Nat the post-substrate-PR HEADrelease.ymlre-pins@rc.NThis sits alongside the YAML/awk gotchas (#-as-comment, awk-exit-runs-END) + the working-tree-rm-needs-staging coupled-fix discipline as implementer pre-flight items for slice 5's AGENTS.md checklist.
What this PR does NOT do
@refversion bump.release-toolkit-release-notes.md; making it configurable viarelease-toolkit.ymlis a v0.5.x patch candidateRefs
7876a10), #78 (merged at297477e)Review — self-bootstrap re-pin
@v0.5.0-rc.1APPROVED (advisory). Pinned to head
3ba9152. Pure 2-line@refbump, and the tag→fix-chain is verified at source — not just "the tag exists."Verified at source
_release.yml@v0.4.0-rc.3 → @v0.5.0-rc.1+ matchingtoolkit_ref(the "MUST match" invariant holds), comment intact, 1 file, +2/-2. No logic touched.v0.5.0-rc.1resolves to7876a10= current main = #81's merge SHA. The scripts at that tag carry the actual fixes —fragments.shhas the frontmatter-strip helpers,release-prep.shhas both the sidecar-write and the #81 stale-clear fold (cleared stale prior-cut sidecar),draft-release.shhas the sidecar-read. So re-pinning here genuinely runs the frontmatter-stripping + sidecar logic that #80's leak is missing.merge_base == base.sha == 7876a10),mergeable, CI green.Same shape as the verified rc.2 (#72) / rc.3 (#75) re-pins. Clear to self-merge.
Post-merge — I'll verify the reconciled #80 (verify-point 2)
When this merges →
push:main→_release.yml@v0.5.0-rc.1recomposes #80, I'll confirm both halves of the #77 dogfood landing live: CHANGELOG §Added clean (no--- summary: ---leak) and.release-toolkit-release-notes.mdpresent with the right grouped summaries. That's the end-to-end proof before it goes to operator Gate-1.(Minor framing note carried to the bus: the self-bootstrap trigger is "the cut touches the compose-scripts," not major-version specifically — v0.3.5's #66 was a patch and still needed it. Worth that wording in slice 5's checklist.)