[ioquatix]

Summary

• Upgrade the existing release integration to bake-gem-github ~> 0.7.0.
• Regenerate the release setup to remove the obsolete signing configuration and GEM_SIGNING_KEY workflow reference.
• Remove the public RubyGems signing certificate and gemspec signing fields. Retain Trusted Publishing and both attestation formats.
• Refresh copyrights through modernize:license in the version-increment hook, matching bake-modernize 0.66.0.

Verification

• bundle exec bake test — 246 tests, 1,232 assertions passed.
• bundle exec rubocop — 61 files, no offenses.
• bundle exec bake decode:index:coverage lib — 256/256 public definitions documented.
• bundle exec bake gem:build — unsigned build succeeds.
• bundle exec bake gem:github:setup:update — no additional changes.
• bundle exec bake gem:github:release:validate base=origin/main — passed.
• Reviewed gem:github:setup:plan; all four rulesets and the rubygems environment already exist, with deployments restricted to main.

Publishing setup

The RubyGems owner can confirm or reuse the existing Trusted Publisher registration with:

bundle exec bake gem:github:setup:publisher key=rubygems

It uses socketry/protocol-http2, release-publish.yaml, and the rubygems environment. Existing matching registrations are reused; MFA may be requested.