chore: update Next.js to 16.2.0

[Lionvsx]

Update Next.js to latest (16.2.0). Run pnpm install after merge.

---

Summary by CodeRabbit

• Chores
  • Updated Next.js and its ESLint configuration to v16.2.0 to ensure compatibility with the latest tooling and improve development workflow.

[coderabbitai]

Warning

Rate limit exceeded

@Lionvsx has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 17 minutes and 35 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 45af53f1-02d6-4251-8d06-48dda707366c

📥 Commits

Reviewing files that changed from the base of the PR and between eb6797c and 0c81a45.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json

Walkthrough

Updated package.json entries for next and eslint-config-next, changing their versions from 15.2.4 to 16.2.0.

Changes

Cohort / File(s)	Summary
Dependency Version Updates package.json	Changed next and eslint-config-next versions from 15.2.4 to 16.2.0 (two-line version updates).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: update Next.js to 16.2.0' directly and clearly describes the main change in the pull request: updating Next.js dependencies from 15.2.4 to 16.2.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/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

• X
• Mastodon
• Reddit
• LinkedIn

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

[devin-ai-integration]

Devin Review found 2 potential issues.

View 1 additional finding in Devin Review.

[devin-ai-integration]

🟡 Stale package-lock.json left behind after switching to pnpm

The PR updates package.json to next@16.2.0 and eslint-config-next@16.2.0, and adds a new pnpm-lock.yaml (indicating a switch to pnpm), but the pre-existing package-lock.json is left in place and still pins next@15.2.4 and eslint-config-next@15.2.4. Having two lock files from different package managers causes ambiguity: deployment platforms like Vercel auto-detect the package manager from lock files and may pick npm over pnpm, leading to installs based on the stale lock file. The package-lock.json should be removed now that pnpm is the intended package manager.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🚩 Major version bump (15→16) with no migration notes or verification

This PR performs a major version jump from Next.js 15 to Next.js 16. Major versions typically include breaking changes. While the current codebase is minimal (just the default template), the project has many dependencies (shadcn/ui components, AI SDK, etc.) that may have peer dependency expectations around Next.js 15. The pnpm-lock.yaml resolved successfully, suggesting no hard peer dependency conflicts, but runtime behavior changes in Next.js 16 (e.g., changes to the App Router, font handling via next/font/google at app/layout.tsx:2, or Image component at app/page.tsx:1) should be verified with a build and smoke test. No specific breaking issue was identified in the code, but this warrants a quick pnpm build verification.

---

Was this helpful? React with 👍 or 👎 to provide feedback.