chore(release): v0.3.0 #13

Closed
forgejo-actions wants to merge 1 commit from release-prep/v0.3.0 into main

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+ dogfood was a conventional-commits feat: → MINOR. From an external-consumer POV the dogfood workflows are internal substrate (no user-facing surface change), so the right commit type was chore: or refactor-equivalent, not feat:.

Closing this PR + the release-prep/v0.3.0 branch will be deleted. Operator will re-dispatch release.yml with bump_override: patch to 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 use chore: vs feat: for internal-infrastructure commits, to save future cuts from this escalation pattern.

— QM, 2026-06-24, per operator (A) ratification.

## 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+ dogfood` was a conventional-commits `feat:` → MINOR. From an external-consumer POV the dogfood workflows are internal substrate (no user-facing surface change), so the right commit type was `chore:` or refactor-equivalent, not `feat:`. Closing this PR + the release-prep/v0.3.0 branch will be deleted. Operator will re-dispatch `release.yml` with `bump_override: patch` to 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 use `chore:` vs `feat:` for internal-infrastructure commits, to save future cuts from this escalation pattern. — QM, 2026-06-24, per operator (A) ratification.
chore(release): prepare v0.3.0
Some checks failed
release-draft / create Forgejo draft release (pull_request) Failing after 4s
release-draft / draft (pull_request) Failing after 0s
c98b83a28e
Generated by release-toolkit release-prep.sh.

Tracker: frankenbit/release-toolkit#1
quartermaster closed this pull request 2026-06-24 19:00:30 +02:00
Some checks are pending
release-draft / create Forgejo draft release (pull_request) Failing after 4s
release-draft / draft (pull_request) Failing after 0s
ac-closure-check / ac-closure check (pull_request)
Required
ac-closure-check / check (pull_request)
Required
changelog-body-check / changelog body Cold-Read linter (pull_request)
Required
changelog-body-check / check (pull_request)
Required
check-self-bootstrap / check (pull_request)
Required
fragment-check / check (pull_request)
Required
fragment-check / coverage (pull_request)
Required
fragment-check / density (pull_request)
Required
gitea-twin-check / check (pull_request)
Required
go-ci / lint + build + test (pull_request)
Required
manifest-check / check (pull_request)
Required
manifest-check / manifest-vs-tag consistency (pull_request)
Required
prep-order-check / check (pull_request)
Required
readme-pin-check / digest (pull_request)
Required
register-check / check (pull_request)
Required
register-check / register-drift check (pull_request)
Required
tests / bats (pull_request)
Required
tests / contract-paths (pull_request)
Required
tests / dated-examples (pull_request)
Required
tests / shellcheck (pull_request)
Required
tests / workflow-schema (pull_request)
Required
toolkit-self-gates / toolkit-self gates (PR's own rt) (pull_request)
Required
workflow-parse-check / check (pull_request)
Required
workflow-parse-check / toolkit-self parse guard and controls (pull_request)
Required
workflow-parse-check / workflow parse and schema (pull_request)
Required

Pull request closed

Sign in to join this conversation.
No description provided.