Repository navigation
Migrate to automated releases with bake-gem-github - #234
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
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.
Move releases to reviewed pull requests:
bake gem:github:release:patchprepares the version and release notes, CI validates the proposed content, and a merged release triggers publication to RubyGems and GitHub.Scaffolded with
bake modernize:releases:githubfrom bake-modernize 0.65.0, followed bybake gem:github:setupfrom bake-gem-github 0.6.0. The change replaces the direct bake-gem dependency, preserves the build and documentation tasks, adds the generated copyright-update hook, removes the duplicate GitHub-release hook, and updates the README command.The generated configuration preserves certificate signing and selects the supported stable Ruby/platform checks, lint, validation, ASan, and Release validation. The proposed rules use the scaffold's default of two PR approvals, dismiss stale approvals, require the latest push to be approved, require up-to-date CI, and protect branch/tag history. These rules apply to all PRs into main when enabled; the review and check rules allow explicit administrator bypass. Environment reviewers are left unmanaged.
Validation
gem:github:setup:updatereturned no changes.gem:github:setup:plan: passed; read-only inspection confirmed the expected publisher settings and that therubygemsenvironment still needs creating.gem:github:release:validate base=77e0c72: passed for this migration commit.77e0c72: “does not block the reactor while waiting for any child process” and “can wait for all child processes”. No runtime code changed.Bootstrap after merge
rubygemsGitHub environment restricted tomainand provide theGEM_SIGNING_KEYmatching the committedrelease.cert.bundle exec bake gem:github:setup:publisher: ownersocketry, repositoryio-event, workflowrelease-publish.yaml, environmentrubygems.bundle exec bake gem:github:setup:planand enable the proposed policy withbundle exec bake gem:github:setup:apply.This PR adds the proposed configuration only; no live rules, publishing credentials, or releases were changed. See the bake-gem-github setup documentation for release preparation and recovery instructions.
Independent of #233; both PRs target main.