chore(deps)(deps): bump react and @types/react in /frontend

[dependabot]

Bumps react and @types/react. These dependencies needed to be updated together.
Updates react from 19.2.6 to 19.2.7

Release notes

Sourced from react's releases.

19.2.7 (June 1st, 2026)

React Server Components

• Fixed missing FormData entries in Server Actions which regressed in 19.2.6 (#36566 by @​unstubbable)

Commits

• 6117d7c Version 19.2.7 (#36591)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react since your current version.

Updates @types/react from 19.2.15 to 19.2.16

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• Chores
  • Updated React and React type definitions to latest patch versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

Frontend React dependencies are updated to patch releases. The react package is bumped from ^19.2.6 to ^19.2.7, and @types/react is bumped from ^19.2.15 to ^19.2.16.

Changes

Frontend React Dependency Updates

Layer / File(s)	Summary
React and type definitions version bumps frontend/package.json	react dependency updated from ^19.2.6 to ^19.2.7, and @types/react dependency updated from ^19.2.15 to ^19.2.16.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• hadleyrich/iscreami#76: Updates @types/react version in frontend/package.json as part of React dependency maintenance.

Poem

🐰 React dances in the patch lane,
Types aligned, clean and plain,
Versions bumped with gentle care,
Seventeen and sixteen share,
Fresh deps make the bundler sing! 🎵

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating react and @types/react dependencies in the frontend directory.
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.

_{✏️ 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 dependabot/npm_and_yarn/frontend/main/multi-c336f0d9c2

---

_{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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/package.json`:
- Around line 18-19: The package.json shows "react" set to ^19.2.7 while
"react-dom" remains ^19.2.6; update the "react-dom" dependency to ^19.2.7 to
match "react" (edit the "react-dom" entry shown in the diff), then
regenerate/update the lockfile so pnpm-lock.yaml resolves react-dom@19.2.7
(e.g., run pnpm install or pnpm up react-dom@19.2.7) to ensure runtime uses
19.2.7.

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

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8bb0f301-2c06-4925-9b18-30828d38d67c

📥 Commits

Reviewing files that changed from the base of the PR and between 908cb5d and 56646b9.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• frontend/package.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check if react-dom 19.2.7 is available on npm
npm view react-dom@19.2.7 version 2>/dev/null || echo "Version 19.2.7 not found"

# Check latest react-dom versions
npm view react-dom versions --json | jq '.[-5:]'

# Verify current react version
npm view react@19.2.7 version

Repository: hadleyrich/iscreami

Length of output: 265

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show the relevant deps in frontend/package.json
echo "== frontend/package.json =="
node -e "const p=require('./frontend/package.json'); console.log({react:p.dependencies?.react||p.devDependencies?.react, reactDom:p.dependencies?.['react-dom']||p.devDependencies?.['react-dom'], typesReact:p.devDependencies?.['`@types/react`']})"

# List likely lockfiles in frontend
echo "== Lockfiles in frontend =="
ls -1 frontend | rg -n 'package-lock\.json|yarn\.lock|pnpm-lock\.yaml|npm-shrinkwrap\.json' || true

# Grep resolved versions in lockfiles (if present)
for f in frontend/package-lock.json frontend/yarn.lock frontend/pnpm-lock.yaml frontend/npm-shrinkwrap.json; do
  if [[ -f "$f" ]]; then
    echo "== Searching $f =="
    rg -n "react-dom@|react-dom:" "$f" | head -n 30 || true
    rg -n "react@|react:" "$f" | head -n 30 || true
  fi
done

Repository: hadleyrich/iscreami

Length of output: 2669

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== package-lock.json: first react-dom occurrences =="
rg -n "react-dom" frontend/package-lock.json | head -n 40 || true

echo "== pnpm-lock.yaml: react-dom resolved version(s) =="
rg -n "react-dom@19\.|react-dom:" frontend/pnpm-lock.yaml | head -n 80 || true

echo "== pnpm-lock.yaml: `@types/react-dom` occurrences =="
rg -n "`@types/react-dom`" frontend/pnpm-lock.yaml | head -n 60 || true

Repository: hadleyrich/iscreami

Length of output: 1831

---

Update react-dom to match react (19.2.7)

frontend/package.json bumps react to ^19.2.7, but react-dom is left at ^19.2.6, and frontend/pnpm-lock.yaml still resolves to react-dom@19.2.6(react@19.2.7), so the runtime dependency won’t pick up the 19.2.7 change your PR calls out. react-dom@19.2.7 exists on npm—align react-dom (and the lockfile) to 19.2.7.

📦 Proposed fix to align react-dom version

     "react": "^19.2.7",
-    "react-dom": "^19.2.6",
+    "react-dom": "^19.2.7",
     "react-router-dom": "^7.16.0",

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"react": "^19.2.7",
	"react-dom": "^19.2.6",
	"react": "^19.2.7",
	"react-dom": "^19.2.7",

🤖 Prompt for 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.

In `@frontend/package.json` around lines 18 - 19, The package.json shows "react"
set to ^19.2.7 while "react-dom" remains ^19.2.6; update the "react-dom"
dependency to ^19.2.7 to match "react" (edit the "react-dom" entry shown in the
diff), then regenerate/update the lockfile so pnpm-lock.yaml resolves
react-dom@19.2.7 (e.g., run pnpm install or pnpm up react-dom@19.2.7) to ensure
runtime uses 19.2.7.