Release core and Redis adapter gems from package-prefixed tags - #183
Merged
Conversation
michal-granec
added this pull request to stack #186
September 11, 2026 13:07
michal-granec
force-pushed
the
release/namespaced-package-tags
branch
from
September 11, 2026 13:12
3d5d0e4 to
3dd60bb
Compare
Push rollout/vX.Y.Z or rollout-redis/vX.Y.Z to test both gems, publish the selected gem, and create its GitHub release. Drop rake release so tagging stays explicit.
michal-granec
force-pushed
the
release/namespaced-package-tags
branch
from
September 11, 2026 13:14
3dd60bb to
f00f7d5
Compare
Authenticate with OIDC instead of a stored API key, and publish the tagged gem without re-running tests in the release workflow.
There was a problem hiding this comment.
🔵 Needs a closer look
Release workflow and Trusted Publishing changes warrant final human verification.
Pull request overview
Updates gem release automation to use package-prefixed tags and RubyGems Trusted Publishing.
Changes:
- Publishes only the gem selected by the tag.
- Adds OIDC authentication and GitHub release creation.
- Updates release documentation and removes obsolete tasks.
File summaries
| File | Summary |
|---|---|
README.md |
Documents package-prefixed release tags. |
Rakefile |
Removes obsolete release tasks. |
.github/workflows/release.yml |
Implements tag-based gem publishing and Trusted Publishing. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
2 tasks
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.
Summary
rolloutfromrollout/vX.Y.Zandrollout-redisfromrollout-redis/vX.Y.Z.Release
rollout/v3.0.0orrollout-redis/v0.1.0).git push origin <tag>.Register the same
release.ymlworkflow as a trusted publisher for both gems. If that publisher specifies a GitHub environment, add the sameenvironment:to this job.