Repository navigation
Verify npm provenance signatures on the Node 24 legs only - #475
Merged
Merged
Conversation
npm 10, bundled with Node 22, lacks the registry's newer signing keys and fails `npm audit signatures` with EMISSINGSIGNATUREKEY for packages attested with them (rolldown, magic-string). The installed tree is the same on every leg, so the check runs once per OS on npm 11.
|
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.



npm audit signaturesfails on the Node 22 legs withEMISSINGSIGNATUREKEY("rolldown@1.2.16 has attestations but no corresponding public key(s)"), as onmainat 29441cb: npm 10, bundled with Node 22, does not know the registry's newer signing keys. The installed tree is identical on every leg, so the step now runs on the 24.x legs (npm 11) only, once per OS.