Repository navigation
Publish gem releases through GitHub Actions. - #5
Merged
Merged
Conversation
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
1 participant
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.
Adopt
bake-gem-githubso maintainers prepare reviewed release PRs and GitHub Actions publishes signed gems through RubyGems Trusted Publishing.Follow the migration guide and the setup used by protocol-http2 and utopia-project. Add the preparation, validation, and publishing workflows generated by
bake-gem-github0.6.0, update the README release command, and use the Socketry signing certificate and local key path. Refresh copyrights, release notes, guides, and the README during the version bump, and let the publisher create GitHub releases. Correct the getting-started guide's unified context/skill commands.The proposed rules require the supported Ruby, lint, coverage, and release-validation checks plus two approvals for all PRs into
main. They allow explicit administrator bypass for reviews/checks and protect branch history and release tags. These are configuration files for review; activate the policy after this PR merges andRelease validationis available.Before the first automated release:
rubygemsGitHub environment restricted tomain. The organizationGEM_SIGNING_KEYis already available to this repository, and the committed public certificate matches the one used by the other migrated gems.socketry/agent-context, workflowrelease-publish.yaml, environmentrubygems, usingbundle exec bake gem:github:setup:publisher.bundle exec bake gem:github:setup:plan, then runbundle exec bake gem:github:setup:applyafter merge.Validated the 86-test suite (245 assertions), RuboCop, documentation coverage, generated configuration, and ordinary-PR release validation. A signed gem build verified against the Socketry certificate, and a separate local release rehearsal generated and independently validated a 0.4.0 candidate. Re-running the setup generator produced no changes.
The gem remains at 0.3.0. After setup, run the Prepare release workflow with
bump=minorto prepare the 0.4.0 release PR with the accumulated changes.