Upgrade Next.js to 16.2.11 - #13
Draft
nahtnam wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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 changed
@next/env, and platform SWC lockfile entriesWhy
GitHub currently reports eight open Dependabot alerts against
docs/package.json(four high, four moderate). Each affects Next.js>=16.0.0 <16.2.11and identifies 16.2.11 as the first patched version.The official Next.js 16.2.11 release lists one additional moderate advisory, for nine upstream security fixes total. This same patch release covers that advisory as well, although Patchworks has no corresponding Dependabot alert.
Impact
The docs app remains on Next.js 16.2 with no source or configuration migration. React, Fumadocs, and other direct dependencies are unchanged.
Verification
bun run --filter @patchworks/docs typecheckbun run --filter @patchworks/docs buildgit diff --checkbun audit --jsoncontains no Next.js 16.2.11 advisory match (it still reports unrelated pre-existing dependency findings outside this PR)Official release: https://github.com/vercel/next.js/releases/tag/v16.2.11