Migrate release workflow to use trusted publisher#2535
Merged
Conversation
Replace the GitHub-release-only workflow with the trusted publisher pattern used by Shopify/spoom and Shopify/rbi. The new workflow publishes the gem to RubyGems.org via OIDC (no API key needed) and then creates a GitHub release. Requires configuring a `release` environment in repo settings and adding a trusted publisher entry on rubygems.org.
paracycle
reviewed
Mar 16, 2026
|
|
||
| - name: Create GitHub release | ||
| run: | | ||
| tag_name="$(git describe --tags --abbrev=0)" |
Member
There was a problem hiding this comment.
Hmm, since this action will be triggered with a tag push, I wonder if there is no way to read the tag that triggered the push instead of trying to find it again in the repository.
Member
There was a problem hiding this comment.
Ah, it is actually what we've been using all along: github.ref or github.ref_name
amomchilov
approved these changes
Mar 16, 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
3 participants
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.
Motivation
Replace the current release workflow with the trusted publisher pattern used by other repos like
Shopify/spoomandShopify/rbi. The new workflow publishes the gem to RubyGems.org via OIDC (no API key needed) and then creates a GitHub release.Implementation
Tests