chore(main): release 0.3.0 - #19
Merged
pmaxhogan merged 2 commits intoJun 26, 2026
Merged
Conversation
Contributor
Coverage
Gate: passed - no coverage regression (epsilon 0.1 pp). |
pmaxhogan
force-pushed
the
release-please--branches--main--components--driven
branch
from
June 26, 2026 01:14
bd14efc to
c7871fa
Compare
pmaxhogan
enabled auto-merge (squash)
June 26, 2026 14:34
pmaxhogan
disabled auto-merge
June 26, 2026 14:38
pmaxhogan
force-pushed
the
release-please--branches--main--components--driven
branch
from
June 26, 2026 14:49
c7871fa to
9d37697
Compare
pmaxhogan
added a commit
that referenced
this pull request
Jun 26, 2026
## Why This repo squash-merges and the squash subject is the PR title, which `release-please` parses as a Conventional Commit. A non-conventional title is silently dropped from the changelog - that's why **#37** ("Comprehensive UI/UX overhaul ...") never made it into the 0.3.0 notes (the release-please step *succeeded*; the parse error was a non-fatal warning). #37 itself has been backfilled to the 0.3.0 release PR (#19) via an empty `feat:` commit, so this PR is purely the going-forward guardrail. ## What - **`.github/workflows/pr-title.yml`** - `amannn/action-semantic-pull-request` validates the PR title on `opened`/`edited`/`synchronize`/`reopened`. Job name `Validate PR title`; to be added to the `main protection` ruleset's required status checks so a bad title blocks merge. - **`CLAUDE.md`** (new, repo-level) - tells Claude to always title PRs as Conventional Commits, documents the squash -> release-please flow, allowed types, breaking-change syntax, and the empty-commit backfill recovery. - Repo setting flipped to squash = **"Pull request title and description"** so the linted PR title is authoritative for every PR (single-commit PRs no longer fall back to the lone commit message). This PR's own title is the dogfood: the new check should run and pass on it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Owner
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.3.0 (2026-06-26)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.