chore(release): v0.30.2 #464
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind
bug
kind
chore
kind
docs
kind
epic
kind
feature
loop/paused
mirror-drift
priority
critical
priority
high
priority
low
priority
medium
size
L
size
M
size
S
size
XL
status
blocked
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
frankenbit/release-toolkit!464
Loading…
Reference in a new issue
No description provided.
Delete branch "release-prep/rolling"
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?
Added
None.
Changed
None.
Deprecated
None.
Removed
None.
Fixed
Cut workflow no longer fails on the not-yet-existent cut tag under the toolkit-self floating-pin discipline. Under #456, the toolkit's own wrapper pins
uses:@main. The reusable then runs from main HEAD.After a rolling-PR merge, main transiently carries
BUILD_BAKED_TOOLKIT_REF='vCUT_TAG'.release-prep.shbakes it at compose so adopters pinning the cut tag get frozen substrate. But the tag itself does not exist yet at push:main time. The oldresolve-refstep emitted that value unconditionally as the checkout target;actions/checkout@v4then failed trying to fetch a not-yet-created tag.Each
resolve-refstep now scope-detects the consumer wrapper'suses:@<ref>value. When it ismain,REFis overridden tomainregardless of the baked value. Adopters are unaffected. Their wrapper pins@vX.Y.Z, the override branch is skipped, and the baked value is trusted as before.Cut-tag artifacts still carry the baked
vCUT_TAGvalue.@vX.Y.Zpins remain a frozen source-of-record per #336. Empirical anchor: v0.30.1 cut failed at7a1e63cb. No action required for adopters. Closes #460.