fix(deps): upgrade next.js and @next/third-parties to 14.2.35 for sec…#51
Merged
Conversation
yeager-eren
approved these changes
Dec 16, 2025
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.
🔒 Critical Security Upgrade: Next.js 14.2.35
This PR updates the
nextand@next/third-partiespackages to version14.2.35to address recent critical security vulnerabilities in the App Router/React Server Components protocol.The target version
14.2.35is the officially patched release for our current Next.js 14 line, as recommended by the Next.js Security Advisory (2025-12-11).Affected Dependencies:
next^14.2.11^14.2.35@next/third-parties^14.2.15^14.2.35Key Vulnerabilities Addressed:
Required Testing:
@next/third-parties) are working correctly.