Skip to content

Verify npm provenance signatures on the Node 24 legs only - #475

Merged
ilovepixelart merged 1 commit into
mainfrom
ci/audit-signatures-modern-npm
Nov 17, 2026
Merged

ilovepixelart merged 1 commit into
mainfrom
ci/audit-signatures-modern-npm

Conversation

@ilovepixelart

Copy link
Copy Markdown
Owner

npm audit signatures fails on the Node 22 legs with EMISSINGSIGNATUREKEY ("rolldown@1.2.16 has attestations but no corresponding public key(s)"), as on main at 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.

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.
@sonarqubecloud

Copy link
Copy Markdown

@ilovepixelart
ilovepixelart merged commit f6a554f into main Nov 17, 2026
15 checks passed
@ilovepixelart
ilovepixelart deleted the ci/audit-signatures-modern-npm branch November 17, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant