Upgrade Next.js to 16.2.11 security release

[BigSimmo]

Summary

• Upgrade next and the direct @next/env dependency from 16.2.10 to 16.2.11.
• Regenerate the npm lockfile and keep the Next.js platform packages aligned.
• Move outstanding issue Save Codex local changes #50 to the resolved archive.

Why

Next.js 16.2.10 is in the affected range for high-severity security advisories fixed by 16.2.11. This is an isolated patch-level dependency update with no application behavior change intended.

Files

• package.json
• package-lock.json
• docs/outstanding-issues.md

Verification

• npm audit --omit=dev --audit-level=high — passed, 0 vulnerabilities.
• npx vitest run tests/check-runtime.test.ts tests/proxy.test.ts tests/proxy-session-refresh.test.ts tests/security-headers.test.ts — 43 passed.
• npm run check:runtime — passed on Node 24.18.0 / npm 11.17.0.
• npm run verify:cheap — passed.
• npm run ensure — project identity verified at the selected local URL.
• npm run verify:ui — passed; production build succeeded and Chromium 265/265 passed.
• npm run verify:pr-local -- --files package.json,package-lock.json,docs/outstanding-issues.md — passed, including lint, typecheck, full unit suite, production build, and offline RAG fixtures.

Checks not run

• Live Supabase, OpenAI, Railway, production database, and live RAG checks were not run because this dependency-only patch does not require provider-backed behavior validation.
• Production readiness was previously attempted in the isolated worktree but could not validate provider credentials because .env.local is intentionally absent there; code-only readiness checks passed.

Risk and rollback

• Risk is limited to a patch-level Next.js runtime change and regenerated platform metadata in the lockfile.
• Rollback is a single-commit revert of this PR.
• No deployment or provider mutation is performed by this PR.

RAG impact: no retrieval behaviour change — framework security patch and lockfile only.

---

Note

Low Risk
Patch-level framework dependency update with no app logic changes; residual risk is limited to Next.js runtime behavior at patch level.

Overview
Patches Next.js off the high-severity advisory range by bumping next and @next/env from 16.2.10 to 16.2.11, with a regenerated package-lock.json so optional @next/swc-* platform binaries stay on the same version.

Outstanding issue #50 is removed from the open table and archived as resolved, noting clean production npm audit, focused framework tests, verify:cheap, and Chromium UI verification.

No application source changes; dev-only Next tooling (e.g. eslint-config-next) remains on 16.2.10.

^{Reviewed by Cursor Bugbot for commit 2cf82e4. Configure here.}

Summary by CodeRabbit

• Bug Fixes

  • Updated Next.js to version 16.2.11, addressing a previously identified high-severity security issue.
  • Confirmed production dependency audits are clean.

• Documentation

  • Updated the issue ledger to archive the resolved security item.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d27f09e-77df-4e6b-bd76-c723f2036b4f

📥 Commits

Reviewing files that changed from the base of the PR and between 2cf82e4 and 73889fa.

📒 Files selected for processing (1)

• docs/production-readiness-checklist.md

📝 Walkthrough

Walkthrough

Next.js is upgraded from 16.2.10 to 16.2.11. Issue #050 is removed from the open issue list and added to the resolved archive with audit and UI verification details.

Changes

Next.js security update

Layer / File(s)	Summary
Upgrade Next.js and archive issue #050 package.json, docs/outstanding-issues.md	Updates next to 16.2.11 and records issue #050 as resolved after the documented audit and UI checks.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: claude

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: a Next.js patch upgrade for a security release.
Description check	✅ Passed	The description includes summary, rationale, files, verification, and risk/rollback, with the key checks documented.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/next-security-16-2-11

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 191: Update the Next.js version reference in
docs/production-readiness-checklist.md from 16.2.10 to 16.2.11, matching the
^16.2.11 runtime target declared by the package.json next dependency.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e6481a48-6b79-4143-b2e1-87a50a6103bd

📥 Commits

Reviewing files that changed from the base of the PR and between 6d5062e and 2cf82e4.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• docs/outstanding-issues.md
• package.json