chore(release): v0.3.5 #68
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!68
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release-prep/v0.3.5"
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?
Fixed
scripts/manifest-check.sh+scripts/release-prep.sh: last-tag detection now skips pre-release tags viagit describe --exclude '*-*'. Without the fix, a pre-release tag (e.g.v0.4.0-rc.1) closer to HEAD than the last stable release falsely tripped manifest-check's tag-vs-manifest step (manifest 0.3.4 BEHIND tag v0.4.0-rc.1) AND silently shiftedrelease-prep.sh'scc_categorize_commits_sincewalk window to the prerelease, dropping conventional-commits content from the cut's CHANGELOG section. Surfaced as a dogfood catch during the v0.4.0 architectural arc — slice 3's bootstrap-tagv0.4.0-rc.1blocked slice 2's CI (#65). The fix is semver-correctness (pre-releases are not releases), not a dogfood-only workaround: any consumer creating their own-rc/-beta/-alphatag would have hit the identical false-failure. Closes #66.8200f34b53to9b83609e5b9b83609e5bee4a9b4fb8