Skip to content

Migrate releases to bake-gem-github. - #61

Merged
ioquatix merged 1 commit into
mainfrom
migrate-bake-gem-github
Oct 23, 2026
Merged

ioquatix merged 1 commit into
mainfrom
migrate-bake-gem-github

Conversation

@ioquatix

Copy link
Copy Markdown
Member

Summary

  • Migrate maintenance dependencies using bake modernize:releases:github from bake-modernize 0.65.0.
  • Generate release preparation, validation, and publishing workflows, release configuration, and native GitHub ruleset payloads with gem:github:setup.
  • Use the existing stable Ruby matrix, RuboCop, coverage, and documentation check names, plus Release validation. Retain certificate signing and the default two-review policy.
  • Refresh copyrights in the version-increment hook, remove the redundant GitHub publishing hook, and update the release command in the readme.

The modernization task updated dependencies but could not merge bake.rb because the local Ollama service was unavailable. The hook was updated directly from the bake-modernize template. The new dependency remains in the existing optional maintenance group.

Verification

  • bundle exec bake test — 207 tests, 581 assertions passed.
  • bundle exec rubocop — 165 files, no offenses.
  • bundle exec bake decode:index:coverage lib — 84/84 public definitions documented.
  • bundle exec bake utopia:project:update — no additional changes.
  • bundle exec bake gem:build signing_key=false — package built successfully.
  • bundle exec bake gem:github:release:validate base=origin/main — passed for this ordinary PR.
  • bundle exec bake gem:github:setup:update — no changes; generated files are current.
  • bundle exec bake gem:github:setup:plan — reviewed current rules and environments.

Setup after merge

The plan currently reports no repository rulesets and no rubygems environment. To enable publishing:

  1. Create the rubygems GitHub environment and restrict it to main.
  2. Register the RubyGems Trusted Publisher for owner socketry, repository protocol-http1, workflow release-publish.yaml, and environment rubygems using bundle exec bake gem:github:setup:publisher.
  3. Make the private key matching release.cert available as GEM_SIGNING_KEY in that environment or an organization secret accessible to this repository.
  4. After the selected CI checks, including Release validation, are available, review bundle exec bake gem:github:setup:plan and run bundle exec bake gem:github:setup:apply as an administrator.

See bake-gem-github setup guidance for details.

Signed-off-by: Samuel Williams <samuel.williams@oriontransfer.co.nz>
@ioquatix
ioquatix merged commit 19c7599 into main Oct 23, 2026
37 of 41 checks passed
@ioquatix
ioquatix deleted the migrate-bake-gem-github branch October 23, 2026 02:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant