fix: update next.js version to 16.0.10 in package.json and pnpm-loc…#356
Closed
mayur9210 wants to merge 1 commit intocgoinglove:mainfrom
Closed
fix: update next.js version to 16.0.10 in package.json and pnpm-loc…#356mayur9210 wants to merge 1 commit intocgoinglove:mainfrom
mayur9210 wants to merge 1 commit intocgoinglove:mainfrom
Conversation
|
@mayur9210 is attempting to deploy a commit to the cgoinglove's projects Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates Next.js from version 16.0.7 to 16.0.10 to address security vulnerabilities referenced in a Next.js security advisory from December 11, 2025.
Key Changes:
- Updated Next.js package version from 16.0.7 to 16.0.10
- Updated all Next.js SWC compiler packages and related dependencies in the lock file
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Updated the Next.js package specification from 16.0.7 to 16.0.10 |
| pnpm-lock.yaml | Updated Next.js version and all related dependencies including platform-specific SWC packages (@next/env, @next/swc-*) and packages that depend on Next.js (better-auth, next-intl, @better-auth-kit/seed) |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Collaborator
|
@mayur9210 mind fixing the conflicts? |
Collaborator
|
The packages in this are just slightly old so it will be easier if I quickly update the core deps. Thanks for your time. |
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.
update next.js version to fix the vulnerabilities.
https://nextjs.org/blog/security-update-2025-12-11