ci: publish to RubyGems on GitHub release#8
Merged
peo-machine merged 1 commit intomainfrom Apr 26, 2026
Merged
Conversation
Triggered by 'release: published'. Verifies the tag matches Threencr::VERSION, runs the test suite, builds the gem, then 'gem push'. RUBYGEMS_API_KEY must be set as a repo secret.
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
2 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.
Summary
Adds `.github/workflows/release.yml` that auto-publishes to RubyGems when a GitHub release is published.
Trigger: `release: published`.
Steps:
Required secret: `RUBYGEMS_API_KEY` (will be set on the repo by the maintainer).
Future migration: RubyGems Trusted Publishing (OIDC) GA'd in 2024; switching removes the long-lived token. Tracked in PLAN.md §6d.
SHA-pinning matches the existing `test.yml` conventions (`actions/checkout`, `ruby/setup-ruby` SHAs).
Test plan