Uh oh!
There was an error while loading. Please reload this page.
test(e2e): Add a static trace lifecycle Next.js routing test app - #23817
Merged
andreiborza merged 2 commits intoSep 1, 2026
Conversation
A new package.json makes every dependency count as added, so dependency review flags advisories the existing app never re-evaluates. 16.2.11 is the first release clearing all high-severity Next.js advisories.
Contributor
size-limit report 📦
|
andreiborza added a commit
that referenced
this pull request
Sep 1, 2026
## What Bumps Next.js in nine E2E test applications off versions carrying high-severity advisories. - `16.2.3` -> `16.2.11` in `nextjs-16`, `nextjs-16-bun`, `nextjs-16-cf-workers`, `nextjs-16-tunnel`, `nextjs-16-trailing-slash` and `nextjs-sourcemaps` - `16.2.6` -> `16.2.11` in `nextjs-16-streaming`, which still hit four of the same advisories - `15.5.18` -> `15.5.21` in `nextjs-15` and `nextjs-15-intl`, matching the pin `packages/nextjs` already uses `16.2.11` and `15.5.21` are 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 Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
andreiborza
marked this pull request as ready for review
September 1, 2026 10:06
chargome
approved these changes
Sep 1, 2026
Uh oh!
There was an error while loading. Please reload this page.
andreiborza
deleted the
ab/add-static-lifecycle-nextjs-routing-e2e-app
branch
September 1, 2026 10:15
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 freeto 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
Adds
nextjs-16-trailing-slash-static, a copy ofnextjs-16-trailing-slashas it stood before #23797 ported it to span streaming, so the static trace lifecycle keeps end-to-end coverage for this group.traceLifecycle: 'static'pins and the transaction-based specs; only the app name changes.latest, turbopackvariant is dropped, so it adds one CI row rather than two. That dimension is already covered by the streamed app.nextis pinned to16.2.11rather than the16.2.3the original uses. A newpackage.jsonmakes every dependency count as added, so dependency review evaluates advisories it never re-checks on the existing app.16.2.11is the first release clearing all high-severity Next.js advisories.Why
Streaming is the default now, but static is still a supported trace lifecycle and nothing would catch a regression in it once each group moves over.
nextjs-16-trailing-slashis the representative for the Next.js client routing group because it covers static, parameterized, nested static, catch-all and home routes.Ref #23513