Skip to content

chore: define changelog sections for release-please#54

Merged
wemeetagain merged 1 commit into
mainfrom
nh/release-please-sections
Jul 20, 2026
Merged

chore: define changelog sections for release-please#54
wemeetagain merged 1 commit into
mainfrom
nh/release-please-sections

Conversation

@nazarhussain

@nazarhussain nazarhussain commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Add an explicit changelog-sections config to release-please-config.json so generated release notes group commits into named sections.

Visible sections: Features, Bug Fixes, Performance Improvements, Code Refactoring, Dependencies, Reverts, Miscellaneous Chores, Documentation.

Hidden types (build, ci, test, style) are marked hidden: true so they don't clutter the changelog.

Motivation

With the default release-please changelog config, only feat and fix map to visible sections; other conventional-commit types (including refactor) are hidden. As a result, #53 (refactor(js): unify env lifecycle refcounting) was merged but did not appear in the open release PR #51, whose changelog only shows the Bug Fixes entry for #50.

Adding refactor → "Code Refactoring" (and the other types above) as visible sections ensures such changes are reflected in future release notes.

Test plan

  • JSON validated (python3 -m json.tool)
  • Config takes effect on the next release-please run

🤖 Generated with Claude Code

Add explicit changelog-sections config so release notes group
commits into named sections, hiding build/ci/test/style types.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@matthewkeil matthewkeil left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@wemeetagain
wemeetagain merged commit 1c5e7b4 into main Jul 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants