chore: define changelog sections for release-please#54
Merged
Conversation
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>
wemeetagain
approved these changes
Jul 20, 2026
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.
Summary
Add an explicit
changelog-sectionsconfig torelease-please-config.jsonso 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 markedhidden: trueso they don't clutter the changelog.Motivation
With the default release-please changelog config, only
featandfixmap to visible sections; other conventional-commit types (includingrefactor) 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 theBug Fixesentry 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
python3 -m json.tool)🤖 Generated with Claude Code