Update nextjs-default e2e fixture lockfile for security advisories - #29926
Merged
Mustapha Jaber (mustjab) merged 1 commit intoJul 28, 2026
Merged
Conversation
Regenerates js/web/test/e2e/exports/testcases/nextjs-default/package-lock.json to pick up the security releases for the pinned dev/test dependencies: next 15.5.18 -> 15.5.22 postcss 8.5.14 -> 8.5.24 nanoid 3.3.12 -> 3.3.16 next 15.5.18 predates the 15.5.21 security release that was 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 within the affected range (<= 8.5.17) for CVE-2026-45623. Lockfile only; package.json ranges (next ^15.0.0, postcss ^8.5.10) are unchanged and the resolved dependency set is identical.
kunal-vaishnavi
approved these changes
Jul 28, 2026
Mustapha Jaber (mustjab)
enabled auto-merge (squash)
July 28, 2026 20:31
Mustapha Jaber (mustjab)
merged commit Jul 28, 2026
688d306
into
microsoft:main
86 of 87 checks passed
This was referenced Aug 12, 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 dev/test npm dependencies in the
nextjs-defaultexporte2e fixture lockfile. Follow-up to #29827, which covered the other five
lockfiles but not this one.
Updates
next15.5.18->15.5.22postcss8.5.14->8.5.24nanoid3.3.12->3.3.16Modified lockfile:
js/web/test/e2e/exports/testcases/nextjs-default/package-lock.jsonnext15.5.18 predates the15.5.21security release co-published with16.2.11, so the fixture still resolved to a version affected by theCVE-2026-64641..64649 advisory batch.
postcss8.5.14 is likewise inside theaffected range (
<= 8.5.17) for CVE-2026-45623.Note the fixture intentionally tracks the
15.xline (next: ^15.0.0inpackage.json, per #28547), so
15.5.22— not16.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
npm audit fix --package-lock-onlyagainstregistry.npmjs.org; verified zeroresolvedURLs point anywhere else.npm audit --package-lock-onlyno longer reportsnextorpostcssadvisories; the diff is a balanced 46 insertions / 46 deletions.
added or dropped.
libcmetadata 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.