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

[recoupableorg]

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.

Summary by CodeRabbit

• Chores
  • Updated Next.js to version 16.2.1 in both the ops and web applications
  • Updated ESLint configuration to version 16.2.1 in both applications

[coderabbitai]

📝 Walkthrough

Walkthrough

Dependencies for Next.js and ESLint configurations were updated across two applications. The next package was bumped from 16.0.10 to 16.2.1, and eslint-config-next was aligned from 14.2.13 to 16.2.1 in both apps/ops and apps/web.

Changes

Cohort / File(s)	Summary
Dependency Updates apps/ops/package.json, apps/web/package.json	Updated next from 16.0.10 to 16.2.1 and eslint-config-next from 14.2.13 to 16.2.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hops of joy for versions new,
Next.js climbs to 16.2,
ESLint in harmony plays along,
Dependencies aligned, steady and strong! ✨

🚥 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 accurately summarizes the main changes: updating Next.js to 16.2.1 and eslint-config-next dependency versions across the codebase.
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 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/web/package.json`:
- Line 35: Update the pinned eslint dependency from "^8" to "^9" to satisfy
eslint-config-next@16.2.1's peer requirement: edit the package.json entries for
the "eslint" field in both the apps/web and apps/ops projects and set "eslint":
"^9"; after changing the version run your package manager to refresh lockfiles
(npm/yarn/pnpm) and verify linting (npm run lint) to confirm no other peer
conflicts remain.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e6462071-ee6f-4ef1-83a8-60add3632c64

📥 Commits

Reviewing files that changed from the base of the PR and between e7c1514 and 91166f7.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• apps/ops/package.json
• apps/web/package.json

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Local versions in apps/web/package.json =="
jq -r '.devDependencies | {eslint, "eslint-config-next": ."eslint-config-next"}' apps/web/package.json

echo
echo "== Local versions in apps/ops/package.json =="
jq -r '.devDependencies | {eslint, "eslint-config-next": ."eslint-config-next"}' apps/ops/package.json

echo
echo "== Peer deps from npm registry for eslint-config-next@16.2.1 =="
curl -s https://registry.npmjs.org/eslint-config-next/16.2.1 | jq '.peerDependencies'

Repository: recoupable/marketing

Length of output: 384

---

Upgrade eslint to ^9 to satisfy eslint-config-next@16.2.1 peer dependency.

eslint-config-next@16.2.1 requires eslint >= 9.0.0 as a peer dependency, but Line 34 pins eslint to ^8. This will cause installation or linting failures. Update both apps/web and apps/ops to use eslint: "^9".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/web/package.json` at line 35, Update the pinned eslint dependency from
"^8" to "^9" to satisfy eslint-config-next@16.2.1's peer requirement: edit the
package.json entries for the "eslint" field in both the apps/web and apps/ops
projects and set "eslint": "^9"; after changing the version run your package
manager to refresh lockfiles (npm/yarn/pnpm) and verify linting (npm run lint)
to confirm no other peer conflicts remain.