chore: re-pin self-bootstrap to v0.27.0-rc.1 (#172) #405
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!405
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "repin/v0.27.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?
Automated self-bootstrap re-pin to
v0.27.0-rc.1(release-toolkit#172, scripts/repin.sh).v0.27.0-rc.1points at a detached bake commit (88611fde0a7f) carryingBUILD_BAKED_TOOLKIT_REF: 'v0.27.0-rc.1'in the reusables; main stays at'main'.uses:@<ref>tov0.27.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).
APPROVED — clean re-pin, completeness verified
Verified the "simple bump" at source (the #327 lesson: simple PRs are where things
slip):
@v0.26.0 → @v0.27.0-rc.1on thejobs.*.uses:line.uses:lines only): all 5 active consumer wrappers now at@v0.27.0-rc.1, zeroremaining
@v0.26.0/@main. The other versions in the ref-census (@v1.0.0,@v0.4.0-rc.1,@v0.2.0,@v0.20.0,@v0.21.0) are all in docstring"Consumer wiring" comment examples, which repin correctly does not touch.
#395 bake-list registration: the ref-pin sweep found it via the registration I
verified, exactly as intended.
Nit (pre-existing, out of #405's scope — future doc-sweep, not a blocker)
The "Consumer wiring" comment examples in the
reusable-*.ymldocstrings havedrifted to inconsistent/stale versions —
reusable-register-check.ymlshows@v1.0.0(not cut yet),reusable-release.ymlshows@v0.4.0-rc.1(ancient),others show
@v0.20.0/@v0.21.0. An adopter copy-pasting an example gets anon-existent or ancient pin. repin doesn't (and shouldn't) touch comments, so this
isn't #405's job — flagging for a future docs pass to normalize the examples to a
current-ish tag. Doesn't gate this merge.
Clear to self-merge.