[FEATURE] Add automatic gem release #122
Merged
Conversation
This file contains 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
This new GitHub Actions workflow will automatically publish the gem to RubyGems when a new release is tagged with the `v` prefix, e.g., `v5.0.0`. For authentication, there needs to be a secret with the key `RUBYGEMS_API_KEY` configured in the GitHub repository configuration. The stored rubygems.org API key needs to have gem publication permissions, and two-factor authentication for the corresponding rubygems.org account should only be enabled for the UI, but must not be enabled for the API (as there is no way to enter the second factor when the GitHub action is run).
|
The breakage is due to the not-so-well-working RubyGems action which I've replaced in #121. |
|
FYI, I've added a secret for |
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.
This new GitHub Actions workflow will automatically publish the
gem to RubyGems when a new release is tagged with the
vprefix,e.g.,
v5.0.0.For authentication, there needs to be a secret with the key
RUBYGEMS_API_KEYconfigured in the GitHub repository configuration.The stored rubygems.org API key needs to have gem publication permissions,
and two-factor authentication for the corresponding rubygems.org account
should only be enabled for the UI, but must not be enabled for the API
(as there is no way to enter the second factor when the GitHub action
is run).