Repository navigation
ci(release): auto-create GitHub Release on tag push - #8
Merged
Merged
Conversation
Adds a github-release job that extracts the matching CHANGELOG section as the release body (falling back to --generate-notes when absent), so future v*.*.* tags produce a GitHub Release alongside the PyPI publish. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
github-releasejob to.github/workflows/release.ymlso futurev*.*.*tag pushes create a GitHub Release alongside the existing PyPI publish.## [x.y.z]section fromCHANGELOG.mdas the release body, falling back to--generate-noteswhen no section is found.github.tokenwithcontents: write— no third-party action or extra secrets.Context: tags
v0.5.1–v0.6.2had been pushed (and published to PyPI) but no GitHub Release was created, becauserelease.ymlonly built + published to PyPI. Those four Releases have now been backfilled manually; this change closes the gap going forward.Test plan
v*.*.*tag and confirm a GitHub Release is created with the CHANGELOG section as its body.🤖 Generated with Claude Code