feat: add release workflow with CHANGELOG generation#6
Merged
Conversation
Owner
Author
|
Tested locally |
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
gh-release.ymltriggered on pushes tomainthat touch source filescommit-and-tag-versionas a dev dependency with commit/tag skipped (workflow handles those)package.json, generates categorizedCHANGELOG.md, commits both back tomain, then creates a GitHub Release using the latest CHANGELOG section as the release bodyWhy
GitHub's auto-generated release notes are a flat list of PR titles in merge order. The CHANGELOG groups changes by type (Features, Bug Fixes, CI, etc.) giving users a much cleaner upgrade story.
Test plan
CHANGELOG.mdCHANGELOG.mdis committed back tomain