update release workflow to publish ruby gem automatically#580
Merged
Conversation
fletchto99
approved these changes
Feb 20, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the GitHub release workflow to automatically publish the secure_headers Ruby gem to RubyGems when a version tag is pushed. The workflow leverages GitHub's OIDC authentication to securely publish to RubyGems without requiring stored API tokens, which aligns with the gem's MFA requirements.
Changes:
- Added
id-token: writepermission to enable OIDC authentication for RubyGems publishing - Added steps to checkout code, set up Ruby environment, and publish the gem using
rubygems/release-gem@v1
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
fletchto99
approved these changes
Feb 20, 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.
All PRs:
Adding a new header
Generally, adding a new header is always OK.
Adding a new CSP directive