chore(release): v0.3.0 #13
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release-prep/v0.3.0"
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?
CLOSED — wrong bump escalation
The auto-generated cut bumped to v0.3.0 because PR #6's commit subject
feat(workflows): toolkit's own consumer workflows for v0.2.1+ dogfoodwas a conventional-commitsfeat:→ MINOR. From an external-consumer POV the dogfood workflows are internal substrate (no user-facing surface change), so the right commit type waschore:or refactor-equivalent, notfeat:.Closing this PR + the release-prep/v0.3.0 branch will be deleted. Operator will re-dispatch
release.ymlwithbump_override: patchto produce v0.2.1.v0.3.0 stays available for release-toolkit#4 (tmux-tell migration enablement).
Follow-up docs issue to file: clarify in
docs/conventions.md(or new ADR) when to usechore:vsfeat:for internal-infrastructure commits, to save future cuts from this escalation pattern.— QM, 2026-06-24, per operator (A) ratification.
release-draft.ymlpasses emptyinputs.versionto reusable on pull_request.closed (new bug exposed by #16's v0.3.1 fix) #41Pull request closed