Skip to content

feat: update Next.js to 16.2.1 and eslint-config-next#1591

Open
recoupableorg wants to merge 1 commit intomainfrom
feat/update-nextjs-16.2
Open

feat: update Next.js to 16.2.1 and eslint-config-next#1591
recoupableorg wants to merge 1 commit intomainfrom
feat/update-nextjs-16.2

Conversation

@recoupableorg
Copy link
Copy Markdown
Collaborator

Upgrades Next.js from 16.0.10 to 16.2.1 (stable release). No breaking changes per release notes — new features include browser log forwarding, dev server lock file, and agent-ready scaffolding.

Upgrades Next.js from 16.0.10 to 16.2.1 (stable release). No breaking
changes per release notes — new features include browser log forwarding,
dev server lock file, and agent-ready scaffolding.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Mar 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
recoup-chat Ready Ready Preview Mar 21, 2026 6:33am

Request Review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 21, 2026

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (2)
  • package.json is excluded by none and included by none
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c90c2a20-6ffc-46f7-a2d4-f5c4b1327dcf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/update-nextjs-16.2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can scan for known vulnerabilities in your dependencies using OSV Scanner.

OSV Scanner will automatically detect and report security vulnerabilities in your project's dependencies. No additional configuration is required.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8ac2417d08

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

"@vitest/coverage-v8": "^4.0.8",
"eslint": "^8",
"eslint-config-next": "14.2.13",
"eslint-config-next": "16.2.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep eslint-config-next compatible with the repo's ESLint major

This upgrade leaves the lint toolchain in an unsupported state: package.json still pins eslint to ^8 on line 126, but the official eslint-config-next@16.2.1 package metadata declares eslint >=9.0.0 as a peer dependency. On clean installs that enforce peers this will fail resolution, and even non-strict installs are now running the Next config against an unsupported ESLint major. Please bump ESLint as part of this change or keep eslint-config-next on a version that still supports ESLint 8.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant