test(e2e): Bump Next.js to 16.2.11 and 15.5.21 in test apps - #23820
Merged
Conversation
These pins carry high-severity Next.js advisories. Dependency review does not catch them because it only evaluates changed manifests, so the pins are never re-checked once committed. Ref #23513 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
andreiborza
marked this pull request as ready for review
September 1, 2026 09:55
Contributor
size-limit report 📦
|
msonnb
approved these changes
Sep 1, 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
2 participants
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.
What
Bumps Next.js in nine E2E test applications off versions carrying high-severity advisories.
16.2.3->16.2.11innextjs-16,nextjs-16-bun,nextjs-16-cf-workers,nextjs-16-tunnel,nextjs-16-trailing-slashandnextjs-sourcemaps16.2.6->16.2.11innextjs-16-streaming, which still hit four of the same advisories15.5.18->15.5.21innextjs-15andnextjs-15-intl, matching the pinpackages/nextjsalready uses16.2.11and15.5.21are the first releases on each line clearing every high-severity advisory. The Next 14 apps are left alone: they pin an old version on purpose to cover the minimum supported version, and their advisory is already allowlisted.Why
Dependency review only evaluates changed manifests, so a pin is checked once when it is introduced and never again. These apps have been sitting on vulnerable versions without CI saying anything, which only surfaced when adding a new app in #23817 made the same dependency count as added.
Ref #23513