chore: adopt conventional commits and grouped release notes - #63
Merged
Conversation
Procrastinate, context providers and the heartbeat thread were missing from the architecture map, and both test commands understated what they need to run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Release notes are generated from PR titles; without categories they land as one flat list. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Release notes come from
generate_release_notes: true, which emits a flat list of PR titles with no grouping. This adds.github/release.ymlcategories and writes the title/commit convention into CLAUDE.md so the format is actually followed.Done out of band, not visible in the diff: the nine type labels (
feat,fix,docs,chore,refactor,perf,test,ci,breaking) already exist on the repo. Each category also lists the pre-existing equivalent (feat+enhancement,fix+bug,docs+documentation), so old labelled PRs group correctly rather than falling through to "Other Changes".Two caveats worth knowing before merging:
.github/release.ymlfrom the default branch, so this does nothing until it lands onmain.Enforcement is deliberately left out. No CI title check, no commit-msg hook — the convention is documented for humans and for Claude sessions, and merges stay unblocked.
The first commit is an unrelated CLAUDE.md accuracy pass (Procrastinate, context providers and the heartbeat thread were absent from the architecture map; both test commands understated their prerequisites — unit tests need Redis, integration tests also need Postgres). Reviewable on its own.
🤖 Generated with Claude Code