Repository navigation
Add RubyGems trusted publishing to the release workflow - #192
Merged
rafaelfranca merged 2 commits intoOct 8, 2026
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
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.
Changes
id-token: writeto the release job.release.rubygems/configure-rubygems-credentialsaction for OIDC authentication.Verification
actionlint1.7.7 passed for.github/workflows/release.yml.gem pushcommand with the resulting token.Required setup
Before the next release, a gem owner must register a trusted publisher for
ejson2env.Shopifyejson2envrelease.ymlreleaseThe workflow does not require a RubyGems API token in the repository secrets.