fix(release): render dependency updates in release notes#42
Conversation
Releases triggered only by chore(deps)/ci(deps) commits (e.g. v1.1.3, v1.2.1) had empty bodies: commit-analyzer cut a patch release via the custom releaseRule, but the default angular preset hides chore/ci commits from the notes. Switch both commit-analyzer and release-notes-generator to the conventionalcommits preset (already installed by the shared release workflow) with an explicit types list that surfaces chore(deps) and ci(deps) under a Dependencies section. The scoped entries must precede the general hidden chore/ci entries because type lookup is first-match-wins. Claude-Session: https://claude.ai/code/session_01EN4tyYEvuDqwHDyxSbyvT8
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdates ChangesRelease configuration changes
Estimated code review effort: 1 (Trivial) | ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Problem
Releases triggered only by
chore(deps)/ci(deps)commits (e.g. v1.1.3, v1.2.1) are published with empty bodies. The customreleaseRulesentry makes commit-analyzer cut a patch release forchore(deps), but release-notes-generator's default angular preset hideschore/cicommits — so the release exists but the notes are blank.Fix
Switch commit-analyzer and release-notes-generator to the
conventionalcommitspreset with an explicitpresetConfig.typeslist that renderschore(deps)andci(deps)under a Dependencies section.Notes:
conventional-changelog-conventionalcommitsis already installed by the sharedkrypsis-io/.githubrelease workflow, so no change is needed there.presetConfig.typesreplaces the default list wholesale (no merging), sofeat/fix/perf/revertmust be re-declared.chore(deps)/ci(deps)entries are placed before the general hiddenchore/cientries.chore(deps) → patchrelease rule is unchanged;ci(deps)still doesn't trigger releases on its own, it just renders when riding along.https://claude.ai/code/session_01EN4tyYEvuDqwHDyxSbyvT8
Summary by CodeRabbit