ci: allow the current release signer in crawlkit's allowlist - #67
Merged
Conversation
Retain the historical key only so previously published tags keep verifying; new release tags use the current signer.
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
1 participant
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.
Allow the current SSH release-signing key to sign new crawlkit tags while retaining the historical v0.14.3 signer solely so previously published tags continue to verify.
This mirrors the two-key transition policy already used by
openclaw/notcrawl. The release-contract test now requires exactly those two reviewed signers.Proof:
buNE...historical andWmI...current SHA-256 fingerprintsmake test-release