Repository navigation
Add RubyGems trusted publishing release workflow - #108
Merged
Merged
Conversation
A push of a vX.Y.Z tag publishes the gem to RubyGems.org through trusted publishing, and then creates a GitHub release for the tag. Update the README to describe the new release process.
paracycle
force-pushed
the
ufuk/rubygems-trusted-publishing
branch
from
October 27, 2026 21:47
c8451e7 to
bf97327
Compare
ScottifyShopson
approved these changes
Oct 27, 2026
3 tasks
This was referenced Oct 27, 2026
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.
Stacked on #107.
Motivation
Releases of Oktakit need a maintainer who runs
bundle exec rake releaselocally with a RubyGems API key. Trusted publishing lets GitHub Actions publish the gem through OIDC, so the repository needs no long-lived RubyGems credential.Changes
Releaseworkflow that starts when avX.Y.Ztag is pushed. The workflow has two jobs:release_gemruns in thereleaseenvironment and publishes the gem withrubygems/release-gem. That action gets a short-lived API key through trusted publishing and adds Sigstore attestations to the gem.release_githubruns afterrelease_gemand creates a GitHub release for the tag, with generated release notes..ruby-version.Setup before the first release
releaseenvironment in the repository settings.oktakitwith repositoryShopify/oktakit, workflowrelease.ymland environmentrelease.Notes
#106 also adds a trusted publishing workflow. Only one of the two PRs must merge, because both workflows start on the same tags and push the same gem version.