fix(ci): use rubygems/release-gem@v1 for OIDC trusted publishing#2
Merged
Conversation
The previous publish step invoked `gem exec rubygems-trusted-publishing`,
which references a gem that doesn't exist on rubygems.org — failing every
release with:
Could not find a valid gem 'rubygems-trusted-publishing' (>= 0)
The rubygems/release-gem@v1 action is the officially-supported way to do
OIDC-based trusted publishing: it requests a token from GitHub's OIDC
provider (using `id-token: write`), exchanges it for a short-lived
rubygems.org API key, and runs `gem build` + `gem push` with that key.
Requirements on the rubygems.org side (already configured for
bybit-exchange/bybit.ruby.api):
- Trusted publisher for the correct repo + workflow filename
- Environment field on rubygems must match the workflow's environment (or
both must be empty — our workflow has no environment)
Also drops the RUBYGEMS_API_KEY fallback: trusted publishing is the only
supported path going forward, and mixing OIDC with an API-key secret would
introduce a confusing race.
Co-Authored-By: Claude Opus 4.7 (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 previous publish step invoked
gem exec rubygems-trusted-publishing, which references a gem that doesn't exist on rubygems.org — failing every release with:The rubygems/release-gem@v1 action is the officially-supported way to do OIDC-based trusted publishing: it requests a token from GitHub's OIDC provider (using
id-token: write), exchanges it for a short-lived rubygems.org API key, and runsgem build+gem pushwith that key.Requirements on the rubygems.org side (already configured for bybit-exchange/bybit.ruby.api):
Also drops the RUBYGEMS_API_KEY fallback: trusted publishing is the only supported path going forward, and mixing OIDC with an API-key secret would introduce a confusing race.