Repository navigation
fix: list every commit type in the release notes - #24
Merged
Merged
Conversation
The angular preset lists only feat, fix, perf and revert, so a release cut by a docs, refactor, ci or chore commit had a version header and nothing under it. The notes now use the conventionalcommits preset with a section for every type in commitTypes. conventional-changelog-conventionalcommits is pinned to 9.3.1 because release-notes-generator loads conventional-changelog-writer 8, which the 10.x preset cannot render with. A package extension makes the pinned preset resolve next to the generator, which otherwise finds the 10.x copy that @commitlint/config-conventional brings in.
…g entry Generated with the repository's own release-notes options from the commits between each pair of release tags.
Mearman
marked this pull request as ready for review
October 29, 2026 10:00
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
|
🎉 This PR is included in version 2.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
The release notes used the angular preset, which only lists feat, fix, perf and revert, so v2.1.1 and v2.1.2 (both cut by ci commits) and v1.1.1 to v1.1.3 had a bare version header and nothing under it, in the GitHub release and in CHANGELOG.md.
The notes now use the conventionalcommits preset with a section for every type in commitTypes, so the types commit-analyzer releases on and the types the notes list come from one list. conventional-changelog-conventionalcommits is pinned to 9.3.1 as a direct devDependency, since release-notes-generator loads writer 8 and the 10.x preset needs writer 9. pnpm hoisted the 10.x copy next to the generator, so a packageExtensions entry in pnpm-workspace.yaml makes it find 9.3.1 first; without it the notes render an error. I ran generateNotes with the real options over a commit of each type for a patch and a minor release, and every type is listed under an H2 version header.
The second commit backfills CHANGELOG.md for those five releases.