Repository navigation
fix(release): trust current maintainer signing key - #314
Merged
Merged
Conversation
Contributor
|
🦞👀 Pull request received. I will update this pull request when review starts. |
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.
What Problem This Solves
The release signer policy does not recognize the current maintainer signing key.
User Impact
The policy now accepts GitHub signing key
1049303forvincentkoc, fingerprintSHA256:OIEOnMWCJeKhWpBNlB42wwPuUG5gsC8Crq1ibnt7ylQ. Existing authorized signers remain valid.Why This Change Was Made
Append the current public key with the
gitnamespace at the canonical policy owner. Preserve all existing entries and release gates.The existing release verifier reads this policy through native Git SSH tag verification; no additional SSH fingerprint or principal restriction needs changing.
Evidence
git diff --checkpassed.openclaw/libopus-wasmv0.5.0tag was rejected by the old policy and accepted by the updated policy with the expected fingerprint and principal.