Separate gem release workflow into two steps #542
Merged
Conversation
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
paracycle
reviewed
Dec 3, 2025
Morriar
reviewed
Dec 4, 2025
1. Release the gem to rubygems.org (manually triggered); this also creates and pushes a new GitHub tag 2. Create and publish a new GitHub release (automatically triggered by tag push)
egiurleo
force-pushed
the
improve-release-workflow
branch
from
8f5073e to
d28dae7
Compare
egiurleo
commented
Dec 4, 2025
egiurleo
changed the title
Morriar
approved these changes
Dec 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Bumping the gem version will be done locally.
If we're happy with this workflow, I'll document it in all the necessary places.