Set L - v0.68.0 cut and Storey adoption
Cut v0.68.0, then get Storey onto release-toolkit. Ordered, because the members are not all pre-cut.
BEFORE THE CUT
- #1578 — the section 11 ASCII gate. In flight as #1579; it changes reusable-workflow log output, which adopters see, so it belongs in the same minor as the coverage input rather than the next one.
- #1564 — runs on EVERY executed cut and calls
rt default-branchwith both override variables inert and before the token is exported. It has not broken a cut, which is why it is worth retiring now: the cut is the worst moment to find out, and it is size/S.
BEFORE STOREY ADOPTS, NOT BEFORE THE CUT
- #1481 —
workflow_dispatchposts no commit status on this forge, so the documented remedy cannot satisfy a required gate. Storey's pin bump and prep PR will drive required contexts; this removes the fallback if one goes missing. - #1480 — an adopter's allowed-kind set decides the version bump invisibly. Storey will write fragments, and its kind set will pick bumps with nothing visible to the author choosing a filename.
THE GOAL
- #1478 — adopt release-toolkit in Storey.
frankenbit/storey#149feeds it: Storey needs a toolkit pin carrying thecoverageinput from #1576, which is on main and ships in this cut.
RELEASE-ADJACENT, AFTER THE CUT
- #1348 — mirror-drift-check's red reaches nobody. A cut fires it on
release: published, and that run cannot grade its own tag (#1445, closed, documented in the workflow header), so the newest release — the one adopters pin — is the one with no drift signal, and a red there is currently unwatched.
Not included: #1473 and #1474 (docs-census chores, high priority but not cut-blocking) and the 20 low-priority trackers.
No due date
33% Completed