chore: upgrade next, react, react-dom

[smakosh]

Upgrade Next.js 16.1.6 → 16.2.3, React/React-DOM
19.2.4 → 19.2.5 across ui, docs, playground, code,
and admin apps.

https://claude.ai/code/session_017ReCUmNvPXVtapFi6o8LeS

Summary by CodeRabbit

• Chores
  • Updated Next.js to version 16.2.3 across packages.
  • Updated React and React DOM to version 19.2.5 across packages.

[coderabbitai]

Walkthrough

This pull request updates Next.js and React runtime dependencies across five application package.json files. Next.js is bumped from version 16.1.6 to 16.2.3, while React and React-DOM are bumped from 19.2.4 to 19.2.5.

Changes

Cohort / File(s)	Summary
Dependency Updates apps/code/package.json, apps/docs/package.json, apps/playground/package.json, apps/ui/package.json, ee/admin/package.json	Bumped next from 16.1.6 to 16.2.3 and react/react-dom from 19.2.4 to 19.2.5 across all application package files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore(admin): update dependencies and remove promo code functionality #1298: Updates the same app package.json files to bump Next.js and React dependencies.
• chore: upgrade next and react #1316: Modifies identical package.json dependency entries (next, react, react-dom) across the same applications.
• chore(docs): adapt docs deps #598: Updates runtime and frontend dependencies including Next.js in the same package files.

Suggested reviewers

• steebchen

🚥 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 pull request title 'chore: upgrade next, react, react-dom' directly and accurately summarizes the main change across all modified files—dependency version upgrades for Next.js, React, and React-DOM.
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 claude/upgrade-nextjs-react-yXo61

---

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

🧹 Nitpick comments (1)

apps/playground/package.json (1)

71-72: Consider consistent version ranges across package.json files.

This file pins React and React-DOM to exact version 19.2.5, while apps/ui/package.json and apps/docs/package.json use the caret range ^19.2.5. This inconsistency may lead to different minor/patch versions being installed across apps in the monorepo.

Consider standardizing on either exact versions (no prefix) or caret ranges (^) for consistency across all apps.

🤖 Prompt for AI Agents

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

In `@apps/playground/package.json` around lines 71 - 72, The playground
package.json pins "react" and "react-dom" to exact versions "19.2.5" which is
inconsistent with apps/ui and apps/docs that use the caret range ^19.2.5; update
the "react" and "react-dom" entries in the apps/playground package.json to use
the same version range used elsewhere (e.g., change to ^19.2.5) or change the
other package.json files to exact versions so all three files use the same
convention, ensuring consistent dependency resolution across the monorepo.

🤖 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/ui/package.json`:
- Line 70: Update the React dependency versions in package.json to a published
release: change the "react" and "react-dom" version strings currently set to
^19.2.5 to ^19.2.1 so they reference the existing 19.2.1 release that is
compatible with Next.js 16.2.3; locate the "react" and "react-dom" entries in
the dependencies block and replace their version constraints accordingly, then
run npm/yarn install to verify resolution.

---

Nitpick comments:
In `@apps/playground/package.json`:
- Around line 71-72: The playground package.json pins "react" and "react-dom" to
exact versions "19.2.5" which is inconsistent with apps/ui and apps/docs that
use the caret range ^19.2.5; update the "react" and "react-dom" entries in the
apps/playground package.json to use the same version range used elsewhere (e.g.,
change to ^19.2.5) or change the other package.json files to exact versions so
all three files use the same convention, ensuring consistent dependency
resolution across the monorepo.

🪄 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: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 27db3d9f-8c3e-404e-b937-612916b6144a

📥 Commits

Reviewing files that changed from the base of the PR and between 53a96ac and 100112c.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (5)

• apps/code/package.json
• apps/docs/package.json
• apps/playground/package.json
• apps/ui/package.json
• ee/admin/package.json