Repository navigation
refactor: Bump npm from 11.20.0 to 11.21.1 - #630
Conversation
|
🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review. Tip
Note Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect. Caution Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #630 +/- ##
=======================================
Coverage 97.77% 97.77%
=======================================
Files 2 2
Lines 225 225
=======================================
Hits 220 220
Misses 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Bumps the transitive dev dependency
npm(the npm CLI) from 11.20.0 to 11.21.1 (lock file only).This is a security update for a development-only dependency. The vulnerable packages are bundled inside
npm(inBundle), so they cannot be updated on their own.npm11.21.1 bundles patched versions:brace-expansionip-addressip-addressip-addresspostcss-selector-parserundicinpmis only required by@semantic-release/npm@13.1.5(range^11.6.2), which runs it in the release workflow. It is not in the production dependency tree, so this does not trigger a release. 11.21.1 is the newest 11.x release; 12.x is outside^11.6.2.Changes
npm dist-tagsupports OIDC authentication (feat(dist-tag): support OIDC authentication npm/cli#10056). It shares the OIDC token exchange withnpm publish, which keeps its provenance auto-configuration. An exchanged token is now set in the non-persistedcliconfig layer instead of theuserlayer.npm stagedocs updated (docs: update npm stage docs to reflect that it can create new packages npm/cli#10050)@npmcli/config@10.14.0(deleting a config override now invalidates cached flattened options, part of feat(dist-tag): support OIDC authentication npm/cli#10056)allowScriptskeys underinstall-strategy=linked(fix: write registry allowScripts keys under install-strategy=linked npm/cli#10059)brace-expansion@5.0.12,ip-address@10.7.2,postcss-selector-parser@7.1.6,undici@6.29.0,http-cache-semantics@4.3.0@npmcli/arborist@9.9.3(fix: write registry allowScripts keys under install-strategy=linked npm/cli#10059, and ETARGET instead of ERESOLVE for unresolvable peer targets, fix(arborist): report ETARGET instead of ERESOLVE for unresolvable peer targets npm/cli#10118);libnpmdiff@8.1.14,libnpmexec@10.3.4,libnpmfund@7.0.28,libnpmpack@9.1.15(arborist bump only)Lock file diff: only
node_modules/npm(version, resolved, integrity, dependency ranges) and its bundlednode_modules/npm/node_modules/*entries change. No entries are added or removed. The bundled versions match npm/cli'spackage-lock.jsonat tagv11.21.1.Breaking Changes
None
Code Changes Required
None — the upgrade is a drop-in replacement.
@semantic-release/npmrunsnpm whoami,npm version,npm publishandnpm dist-tag addfrom the localnode_modules(preferLocal). The release workflow (release-automated.yml) authenticates withNPM_TOKEN, does not grantid-token: writeand does not enable provenance. So for bothpublishanddist-tag, npm's OIDC exchange returns early ("Skipped because incorrect permissions for id-token within GitHub workflow") and token authentication is unchanged. The bundledundiciis only used bynode-gyp, not by the registry or publish code path. The engines requirement (^20.17.0 || >=22.9.0) is the same as in 11.20.0 and is satisfied by the release workflow (Node 24) and the CI matrix (Node 20.18, 20.19, 22.12, 24.11). PR CI does not run these commands.Summary by CodeRabbit