Add release publishing script - #236
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
bin/publish-release.rb takes a release tag, resolves it to the CI run that built the gems, and publishes the artifacts: gems and GPG-signed checksums to the versioned S3 path, the S3-hosted RubyGems index, and the HTML docs to the docs bucket. It runs dry by default and reaches RubyGems.org — the one irreversible step — only after the S3 artifacts are verifiable and the release version is retyped to confirm. Configuration (GitHub token, AWS and bucket settings) lives in an owner-only XDG config file, shared out of band so any maintainer can cut a release.
DemetrisChr
approved these changes
Jul 3, 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.
bin/publish-release.rb takes a release tag, resolves it to the CI run that built the gems, and publishes the artifacts: gems and GPG-signed checksums to the versioned S3 path, the S3-hosted RubyGems index, and the HTML docs to the docs bucket. It runs dry by default and reaches RubyGems.org — the one irreversible step — only after the S3 artifacts are verifiable and the release version is retyped to confirm.
Configuration (GitHub token, AWS and bucket settings) lives in an owner-only XDG config file, shared out of band so any maintainer can cut a release.