Create a GitHub Release when pushing a gem#1198
Merged
Merged
Conversation
rubygems/release-gem pushes the version tag and publishes to RubyGems but does not open a GitHub Release, so the Releases page had to be updated by hand after each release. Add a step that creates a Release for the tag it just pushed, with notes generated from merged PRs. Prerelease versions (like 1.0.0.rc1) are flagged with --prerelease via Gem::Version#prerelease? so they do not show as Latest or steer gem install users toward them.
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 Push Gem workflow publishes the gem and pushes the version tag through
rubygems/release-gem, but it never opened a GitHub Release, so the Releases page had to be updated by hand after each release.This adds a step that runs after
release-gemand creates a Release for the tag it just pushed. It uses--generate-notesfor the body and--verify-tagso it only ever targets a tag that already exists on the remote. WhenSimpleCov::VERSIONis a prerelease (Gem::Version#prerelease?is true, as for1.0.0.rc1) the Release is marked--prerelease, so release candidates do not appear as Latest or nudgegem installusers toward them. Final versions get a normal Release.