Upgrade nextjs #81
Merged
Upgrade nextjs #81
Conversation
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR upgrades Next.js from version 15.1.6 to 16.0.7 to address security vulnerabilities CVE-2025-55182 and CVE-2025-66478. The upgrade includes updates to related dependencies and configuration changes to align with Next.js 16 requirements.
Key changes include:
- Next.js upgraded to version 16.0.7 with corresponding dependency updates (next-auth, nodemailer)
- TypeScript JSX compilation mode changed from "preserve" to "react-jsx" to support the new JSX transform
- ESLint configuration updated with explicit ignores and custom rules, with eslint command modified for better caching
Reviewed changes
Copilot reviewed 3 out of 5 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Upgrades Next.js to 16.0.7, next-auth to beta.30, nodemailer to 7.0.11, and updates eslint command for improved caching |
| tsconfig.json | Updates JSX compiler to "react-jsx", reformats configuration arrays, and adds .next/dev/types path to includes |
| eslint.config.mjs | Adds explicit ignore patterns and disables @typescript-eslint/no-require-imports rule |
| Dockerfile | Changes base image from node:23-alpine3.20 to node:23-slim for better compatibility |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "lucide-react": "^0.474.0", | ||
| "next": "15.1.6", | ||
| "next-auth": "^5.0.0-beta.25", | ||
| "next": "^16.0.7", |
There was a problem hiding this comment.
The Next.js version has been upgraded to ^16.0.7, but eslint-config-next on line 74 is still at version 15.1.6. These should be kept in sync. Update eslint-config-next to match the Next.js version (e.g., ^16.0.7).
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.
Mitigating https://community.vercel.com/t/security-advisory-for-cve-2025-55182-and-cve-2025-66478/29095