Create GitHub releases automatically on tag push - #8
Merged
Conversation
Pushing a v* tag now creates the matching GitHub release with auto-generated notes. Gem publishing stays with `rake release`. Co-Authored-By: Claude Opus 5 (1M context) <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
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.
The
v0.4.0tag was pushed, but the Releases page still showed 0.3.1 as latest — a git tag isn't a GitHub Release, and nothing was creating the Release object.This adds
.github/workflows/release.yml, which fires on anyv*tag push and creates the matching release with auto-generated notes.github.tokenwithcontents: write, so there's no secret to configure.vprefix (v0.4.0→0.4.0) to match existing releases.rake releasealready handles build, tag, andgem push, and duplicating it here would conflict.Notes come from GitHub's generate-notes API, which lists merged PR titles since the previous release. If release-prep PRs become noise in that list, a
.github/release.ymlwith label-based exclusions can filter them without touching this workflow.The 0.4.0 release itself was created manually, since its tag predates this workflow.
🤖 Generated with Claude Code