chore(ci): validate non-EOL releases are signed with an "active" key #43
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
aduh95
force-pushed
the
add-ci-for-active-release-lines
branch
from
9655346 to
c8a2744
Compare
juanarbol
approved these changes
Jul 14, 2025
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 goal would be to recommend folks to use
gpg-only-active-keys/pubring.kbxas the source of truth for verifying Node.js releases. For that, we'd need to ensure the keyring is always able to verify the supported versions, which this workflow should help us do that.That means if a releaser needs to change the key listed as theirs, and that key was used to sign one the latest release, they can't do that until another release on that release line, or until said release line reaches EOL.