fix(deps): update nextjs monorepo (16.2.9 → 16.2.10)

[its-miso]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-next (source)	16.2.9 → 16.2.10
next (source)	16.2.9 → 16.2.10

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

vercel/next.js (eslint-config-next)

v16.2.10

Compare Source

Contains no changes except publishing @next/swc-wasm-web which was accidentally not published since 16.2.4.

---

Configuration

📅 Schedule: (in timezone America/Edmonton)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_low_confidence)

Review: Next.js 16.2.9 → 16.2.10 Dependency Upgrade

Summary

This PR upgrades the Next.js monorepo packages from version 16.2.9 to 16.2.10. The change is a patch-level update affecting next, eslint-config-next, and all platform-specific @next/swc-* packages.

---

Required Checks

✅ check for breaking API changes in updated dependencies

Verified: The official Next.js v16.2.10 release notes explicitly state: "Contains no changes except publishing @next/swc-wasm-web which was accidentally not published since 16.2.4." This release contains only a publishing fix for a WASM package and introduces no code changes or API modifications. The GitHub compare view (vercel/next.js@v16.2.9...v16.2.10) shows only 4 commits, all related to workflow changes and documentation—not application code. No breaking API changes exist in this upgrade.

✅ run full test suite after upgrade

Verified: The CI Check Results table confirms all checks passed for this commit:

• Docker Build: completed, success
• Tests: completed, success
• Lint: completed, success
• Build: completed, success
• Typecheck: completed, success

The full test suite ran and passed after the dependency upgrade.

---

Standards Compliance

This PR follows repository conventions:

• Dependency updates via Renovate: This PR was generated by renovatebot, the automated dependency update system (confirmed from PR metadata and body)
• Minimal diff: Only package-lock.json changed, as expected for a clean dependency version bump
• CI gate required: All required CI checks (Tests, Lint, Build, Typecheck) passed before this review

---

Evidence Provider Findings

No evidence providers are configured for this repository.

---

Tool Harness Findings

The tool harness ran successfully. Key findings:

• package.json read confirmed: Next.js version constraint is ^16.2.7, engines require node >= 24
• Next.js v16.2.10 release metadata fetched from GitHub API confirms: "Contains no changes except publishing @next/swc-wasm-web which was accidentally not published since 16.2.4"

---

Unknowns / Needs Verification

None. All evidence is complete and confirms the upgrade is safe.

---

Recommendation

Approve. This is a safe patch-level upgrade with:

• No breaking API changes (explicitly documented in release notes)
• All CI checks passing (Tests, Lint, Build, Typecheck, Docker Build)
• Minimal risk (same minor version, patch-only change)

The PR satisfies all required checks and meets repository standards for dependency updates.