Repository navigation
Migrate gem signing to the Socketry certificate - #236
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.
The v1.22.2 release merged successfully, but publishing stopped before building or uploading the gem because the organization's
GEM_SIGNING_KEYdoes not match io-event's old personalrelease.cert.Migrate to the shared Socketry certificate using
bundle exec bake modernize:signing. The generator selects~/.gem/socketry-release.certfrom the gem's GitHub owner. Update the gemspec's local signing-key path to~/.gem/socketry-release.pem, add the release note, and regenerate the README withutopia:project:update.The public certificate identifies
/O=Socketry/CN=Socketry Ruby Gemsand expires on 2027-09-21. Its SHA256 fingerprint is93da798e45600ed06c90ce3014e7b8a0beb28278d32ca8d2c7aba6c410d76899. The matching local Socketry key was checked without printing or committing private-key material. GitHub secret values cannot be read back; the existing organization secret remains unchanged.Validation:
HighSecuritypolicy in a temporary trust directory, including exact agreement between the embedded signer andrelease.cert.git diff --checkpassed.After merge, prepare the next patch release (v1.22.3). Re-running the failed v1.22.2 publisher would still use that release's old certificate, because publication is pinned to the merged release commit. This PR does not publish a gem or alter existing tags.