ci: migrate to npm 12 - #45
Merged
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
npm 12 disables dependency install scripts (plus git and remote-URL dependencies) by default — see the npm v12.0.0 release notes. This migrates CI to npm 12.
setup-nodein both the verify matrix and the release job — no Node.js release bundles npm 12 yet. All matrix Node versions (22 / 24 / 26) satisfy npm 12's^22.22.2 || ^24.15.0 || >=26.0.0range when resolved to current patches.npm publishis unchanged: the release job already uses OIDC (id-token: write) with--provenance, which is exactly where npm's tooling is heading.Verified against the lockfile: only fsevents and msw have install scripts, both safe to leave blocked (msw's postinstall only matters for browser worker setup). No git or remote-URL dependencies.
Part of the org-wide npm 12 CI migration.