Update npm lockfiles to latest versions - #29827
Merged
kunal-vaishnavi merged 1 commit intoJul 23, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (5)
- js/package-lock.json: Generated file
- js/react_native/e2e/package-lock.json: Generated file
- js/react_native/package-lock.json: Generated file
- js/web/package-lock.json: Generated file
- onnxruntime/test/wasm/package-lock.json: Generated file
kunal-vaishnavi
approved these changes
Jul 23, 2026
kunal-vaishnavi
enabled auto-merge (squash)
July 23, 2026 00:42
Mustapha Jaber (mustjab)
added a commit
that referenced
this pull request
Jul 28, 2026
…29926) ## Description Updates vulnerable dev/test npm dependencies in the `nextjs-default` export e2e fixture lockfile. Follow-up to #29827, which covered the other five lockfiles but not this one. ## Updates - `next` `15.5.18` -> `15.5.22` - `postcss` `8.5.14` -> `8.5.24` - `nanoid` `3.3.12` -> `3.3.16` Modified lockfile: - `js/web/test/e2e/exports/testcases/nextjs-default/package-lock.json` `next` 15.5.18 predates the `15.5.21` security release co-published with `16.2.11`, so the fixture still resolved to a version affected by the CVE-2026-64641..64649 advisory batch. `postcss` 8.5.14 is likewise inside the affected range (`<= 8.5.17`) for CVE-2026-45623. Note the fixture intentionally tracks the `15.x` line (`next: ^15.0.0` in package.json, per #28547), so `15.5.22` — not `16.2.11` — is the correct target. No package manifests or runtime source files are changed. The resolved dependency set is unchanged (identical package keys before/after); the diff is purely `version`/`resolved`/`integrity`. ## Validation - Regenerated with `npm audit fix --package-lock-only` against `registry.npmjs.org`; verified zero `resolved` URLs point anywhere else. - `npm audit --package-lock-only` no longer reports `next` or `postcss` advisories; the diff is a balanced 46 insertions / 46 deletions. - Confirmed package key sets are identical pre/post, so no dependency was added or dropped. - Preserved `libc` metadata that npm >= 11.6 drops when rewriting lockfiles (the packages still declare it), keeping musl/glibc optional-dep selection intact for the `@next/swc-linux-*` binaries.
This was referenced Aug 12, 2026
This was referenced Sep 1, 2026
This was referenced Sep 9, 2026
Open
This was referenced Sep 16, 2026
This was referenced Sep 23, 2026
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.
Description
Updates vulnerable transitive npm dependencies in ONNX Runtime lockfiles.
Updates
brace-expansion1.x ->1.1.16brace-expansion2.x ->2.1.2brace-expansion5.x ->5.0.7js-yaml3.x ->3.15.0js-yaml4.x ->4.3.0Modified lockfiles:
js/package-lock.jsonjs/react_native/package-lock.jsonjs/react_native/e2e/package-lock.jsonjs/web/package-lock.jsononnxruntime/test/wasm/package-lock.jsonNo package manifests or runtime source files are changed. The
js-yamlupdate also refreshes its generated transitiveargparsemetadata.Validation
npm update --package-lock-only --ignore-scriptsusingregistry.npmjs.org.npm install --package-lock-only --ignore-scriptsin all five affected directories; lockfiles remained stable.npm audit --package-lock-onlyin all five directories; neitherbrace-expansionnorjs-yamlremains in advisory output.