chore: upgrade next and react

[smakosh]

Summary by CodeRabbit

• Chores
  • Updated Next.js to version 16.0.9 across all applications
  • Updated React and React DOM to version 19.2.2 across all applications for stability improvements

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Dependency version updates across four app package.json files in a monorepo. Next.js bumped from 16.0.3–16.0.7 to 16.0.9, and React and React-DOM bumped to 19.2.2 versions across all apps.

Changes

Cohort / File(s)	Change Summary
Next.js and React version bumps apps/admin/package.json, apps/docs/package.json, apps/playground/package.json, apps/ui/package.json	Updated Next.js to 16.0.9, React to 19.2.2 (or ^19.2.2), and React-DOM to 19.2.2 (or ^19.2.2) across all four apps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify compatibility of Next.js 16.0.9 and React 19.2.2 with existing application code across all apps
• Check for any documented breaking changes in bump from 16.0.3/16.0.7 to 16.0.9 and from 19.2.0/19.2.1 to 19.2.2
• Confirm consistent versioning strategy across apps (some use caret ranges like ^19.2.2, others use exact pinned versions)

Possibly related PRs

• chore: back 2 webpack #1299 — Modifies the same Next.js and React dependency entries in apps/admin, apps/playground, and apps/ui
• chore(docs): adapt docs deps #598 — Updates dependencies in apps/docs/package.json, including the Next.js version

Suggested reviewers

• steebchen

Pre-merge checks and finishing touches

✅ 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: upgrade next and react' accurately summarizes the main change—updating Next.js and React dependencies across multiple package.json files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/upgrade-next-react

---

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: 0

🧹 Nitpick comments (3)

apps/admin/package.json (1)

50-50: Approve dependency updates; consider aligning eslint-config-next version.

The Next.js, React, and React-DOM patch updates are safe. However, line 69 pins eslint-config-next to 16.0.0 while next is bumped to 16.0.9. While patch-level skew is typically safe for linting configs, consider updating eslint-config-next to match the next version for consistency.

Also applies to: 55-56

apps/playground/package.json (1)

57-57: Approve dependency updates; consider aligning eslint-config-next version.

Patch updates to Next.js and React are safe. Like apps/admin, line 85 pins eslint-config-next to 16.0.0 while next is 16.0.9. Consider updating to 16.0.9 for consistency across the monorepo.

Also applies to: 64-65

apps/ui/package.json (1)

65-65: Approve dependency updates; note version specifier inconsistency in monorepo.

The patch updates are safe. However, this app uses caret versions (^19.2.2, ^19.2.1) while apps/admin and apps/playground use exact versions (19.2.2, 19.2.1). Consider aligning version specifiers across all apps for consistency, unless there is a deliberate reason (e.g., different stability/patch policies per app).

Also applies to: 73-74

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0a8f9b1 and a751e7d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• apps/admin/package.json (1 hunks)
• apps/docs/package.json (1 hunks)
• apps/playground/package.json (1 hunks)
• apps/ui/package.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.{ts,tsx,js,jsx,json,md}

📄 CodeRabbit inference engine (CLAUDE.md)

Always use tabs for indentation

Files:

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

🧠 Learnings (3)

📚 Learning: 2025-12-03T12:42:26.162Z

Learnt from: CR
Repo: theopenco/llmgateway PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-03T12:42:26.162Z
Learning: Applies to apps/{ui,playground,docs}/**/*.{ts,tsx} : Use `next/link` for links and `next/navigation`'s router for programmatic navigation

Applied to files:

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

📚 Learning: 2025-12-03T12:42:14.219Z

Learnt from: CR
Repo: theopenco/llmgateway PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T12:42:14.219Z
Learning: Applies to apps/{ui,playground}/**/*.{tsx} : Use `next/link` for links and `next/navigation`'s router for programmatic navigation

Applied to files:

• apps/playground/package.json
• apps/docs/package.json
• apps/ui/package.json

📚 Learning: 2025-12-03T12:42:14.219Z

Learnt from: CR
Repo: theopenco/llmgateway PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T12:42:14.219Z
Learning: Applies to apps/{ui,playground}/**/*.{ts,tsx} : Use Next.js App Router with React Server Components for frontend development

Applied to files:

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

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)

• GitHub Check: build-split (playground, linux/amd64)
• GitHub Check: build-split (admin, linux/amd64)
• GitHub Check: build-split (worker, linux/amd64)
• GitHub Check: build-split (ui, linux/amd64)
• GitHub Check: build-split (api, linux/amd64)
• GitHub Check: build-split (gateway, linux/amd64)
• GitHub Check: build-split (docs, linux/amd64)
• GitHub Check: build-unified (linux/amd64)
• GitHub Check: generate / run
• GitHub Check: lint / run
• GitHub Check: build / run
• GitHub Check: test / run
• GitHub Check: autofix

🔇 Additional comments (1)

apps/docs/package.json (1)

31-31: Approve dependency updates; verify fumadocs compatibility post-upgrade.

The patch and minor version updates are safe and low-risk. The docs app sees a larger next version jump (16.0.3 → 16.0.9, +6 patches), but all remain within the safe 16.0.x family. React and React-DOM are updated consistently with ui app (caret versions).

Since this app uses fumadocs for documentation generation, verify that fumadocs (16.0.11, line 28) is compatible with next 16.0.9 and run the docs build (pnpm build) to confirm no regressions.

Also applies to: 33-34