chore: create GitHub release with generated notes#20
Merged
Conversation
Use GitHub-generated release notes and skip duplicate publish/release steps on reruns.
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
1 participant
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.
What is this?
This PR extends the release workflow so tag pushes create a GitHub Release after npm publication, with the release description populated from GitHub-generated release notes instead of a hand-written body.
How does it work?
The workflow now checks whether the package version is already published on npm and skips
npm publishon reruns. After that, it usesgh release viewto avoid duplicate releases andgh release create --generate-notes --verify-tagto create the release entry with GitHub-generated notes.Why is this useful?
It automates the full release path in one workflow, keeps release notes aligned with GitHub’s own generator, and makes the job recoverable if a prior run published the package but failed before creating the release.