Repository navigation
fix: authorize maintainer release tag signing key - #7
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Authorize the existing maintainer GitHub SSH public key for signed release tags, as explicitly approved by the user. Append the key under the existing release principal and Git namespace; retain the original trusted key and all tag, main-ancestry, release verification and environment approval rules.
Public key fingerprint:
SHA256:+TkH1K2uhAJ/ftzDiWtLCBM/VLWfOxE+12o0pxDBJ+g. No private key is stored in the repository.Validation: verify an actual SSH signature against each updated allowlist; required repository PR checks. Runtime source is unchanged from the previously accepted release preparation.