ci: Publish to RubyGems with trusted publishing - #150
Merged
Merged
Conversation
The API key path cannot publish unattended: the owning account requires an OTP for API pushes, which is why the 2.7.0 and 2.8.0 publish jobs failed. Exchange the job's OIDC token for a RubyGems credential instead, which also lets release-gem attach attestations.
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 API key publish can't run unattended: the owning rubygems.org account requires an OTP for API pushes, so both the 2.7.0 and 2.8.0 publish jobs died at
gem push. Switch the job to trusted publishing:id-token: write, noGEM_HOST_API_KEY, and release-gem's default OIDC setup. This also enables the attestation it was warning about.Requires a trusted publisher on the gem's rubygems.org page for
sourcelevel/faraday-http-cache, workflowrelease-please.yml, no environment. After this merges and that's configured, aworkflow_dispatchon master publishes the already-tagged 2.8.0.