docs: correct the release process - #286
Merged
Merged
Conversation
bsneed
approved these changes
Sep 29, 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
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.
The old text said "we automatically push tags to Rubygems via CI" and ended with "run the publish action on Github", neither of which matches how 2.6.0 shipped.
Publishing is triggered by creating a GitHub Release, not by pushing a tag or running an action manually, and the
productionenvironment requires review before the job proceeds. Also records the three trusted-publisher fields that must match the workflow, since a mismatch fails at the OIDC exchange with nothing useful in the log.