chore(deps): bump react from 19.2.4 to 19.2.5 in /docs

[dependabot]

Bumps react from 19.2.4 to 19.2.5.

Release notes

Sourced from react's releases.

19.2.5 (April 8th, 2026)

React Server Components

• Add more cycle protections (#36236 by @​eps1lon and @​unstubbable)

Commits

• 23f4f9f 19.2.5
• 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)

[dependabot]

Labels

The following labels could not be found: npm. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[greptile-apps]

Greptile Summary

This Dependabot PR bumps react from 19.2.4 to 19.2.5 in the /docs Docusaurus site. The single change in 19.2.5 is additional cycle protections for React Server Components.

• react-dom is left at 19.2.4 while react moves to 19.2.5 — React and ReactDOM must always be at the same version and are published together by the React team. The lockfile resolves as react-dom@19.2.4(react@19.2.5), confirming the mismatch. react-dom should be bumped to 19.2.5 as well.

Confidence Score: 4/5

Safe to merge for a docs-only site but react-dom should be bumped to 19.2.5 to match react before landing.

A P1 version mismatch exists between react (19.2.5) and react-dom (19.2.4) — they must be kept in sync per React's own requirements. The mismatch is patch-level and in a docs build so runtime risk is low, but it should be corrected for correctness.

docs/package.json — react-dom version needs to be updated to 19.2.5.

Important Files Changed

Filename	Overview
docs/package.json	Bumps react to 19.2.5 but leaves react-dom at 19.2.4, introducing a version mismatch between the two tightly coupled React packages.
docs/pnpm-lock.yaml	Lockfile updated consistently to resolve all peer dependencies against react@19.2.5; react-dom resolves as 19.2.4(react@19.2.5) confirming the version mismatch.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[docs/package.json] --> B[react 19.2.5 ✅]
    A --> C[react-dom 19.2.4 ⚠️]
    B -- "peer dep" --> D[react-dom should match]
    C -. "mismatch" .-> D
    D --> E[react-dom 19.2.5 needed]

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: docs/package.json
Line: 32

Comment:
**`react-dom` not bumped alongside `react`**

`react` and `react-dom` are tightly coupled and must always be at the same version — the React team publishes them together. This PR bumps `react` to 19.2.5 but leaves `react-dom` pinned at 19.2.4, creating a version mismatch. While the lockfile resolves `react-dom@19.2.4(react@19.2.5)` and may work at the patch level, this is contrary to React's own guidance and could cause subtle runtime issues (e.g. mismatched internal shared state, concurrent mode behavior, event delegation differences).

```suggestion
    "react-dom": "19.2.5"
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "chore(deps): bump react from 19.2.4 to 1..." | Re-trigger Greptile}

[greptile-apps]

react-dom not bumped alongside react

react and react-dom are tightly coupled and must always be at the same version — the React team publishes them together. This PR bumps react to 19.2.5 but leaves react-dom pinned at 19.2.4, creating a version mismatch. While the lockfile resolves react-dom@19.2.4(react@19.2.5) and may work at the patch level, this is contrary to React's own guidance and could cause subtle runtime issues (e.g. mismatched internal shared state, concurrent mode behavior, event delegation differences).

Suggested change

	"react-dom": "19.2.4"
	"react-dom": "19.2.5"

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/package.json
Line: 32

Comment:
**`react-dom` not bumped alongside `react`**

`react` and `react-dom` are tightly coupled and must always be at the same version — the React team publishes them together. This PR bumps `react` to 19.2.5 but leaves `react-dom` pinned at 19.2.4, creating a version mismatch. While the lockfile resolves `react-dom@19.2.4(react@19.2.5)` and may work at the patch level, this is contrary to React's own guidance and could cause subtle runtime issues (e.g. mismatched internal shared state, concurrent mode behavior, event delegation differences).

```suggestion
    "react-dom": "19.2.5"
```

How can I resolve this? If you propose a fix, please make it concise.

[claude]

🟡 This PR bumps react to 19.2.5 but leaves react-dom at 19.2.4, creating a version mismatch that is explicitly unsupported by the React team. The fix is to also bump react-dom to 19.2.5 in docs/package.json.

Extended reasoning...

What the bug is and how it manifests

docs/package.json specifies react at 19.2.5 while react-dom remains pinned at 19.2.4. The React team explicitly requires react and react-dom to be on the same version — this is a documented requirement enforced through peer dependencies. Mixing versions can cause hydration failures, warnings like "react-dom is not compatible with this version of React", or other subtle runtime errors.

The specific code path that triggers it

In docs/package.json (lines 31–32):

"react": "19.2.5",
"react-dom": "19.2.4"

The lock file confirms the mismatch is real and was resolved: react-dom@19.2.4(react@19.2.5) — meaning react-dom 19.2.4 is installed against react 19.2.5.

Why existing code doesn't prevent it

Dependabot only bumped the react dependency and did not update react-dom in the same PR. pnpm resolved the combination without emitting a hard error because react-dom declares react as a peer dependency with a permissive range (e.g., >=15), not an exact version match. This means the mismatch silently passes the install step even though it violates the React team's release contract.

What the impact would be

While this is a docs-only Docusaurus site and the react 19.2.5 change (RSC cycle protections) is unlikely to directly affect react-dom behavior, the version mismatch is a policy violation. In practice it may cause no visible issues on this patch bump, but it sets a precedent for version drift and could trigger warnings or subtle differences in future patch releases.

How to fix it

Update react-dom to 19.2.5 in docs/package.json and regenerate the lock file:

"react": "19.2.5",
"react-dom": "19.2.5"

Then run pnpm install to update the lock file.

Step-by-step proof

1. Open docs/package.json — react is 19.2.5 (changed by this PR), react-dom is 19.2.4 (not changed).
2. Open docs/pnpm-lock.yaml — the react-dom specifier entry still reads specifier: 19.2.4 and the snapshot key is react-dom@19.2.4(react@19.2.5), confirming react-dom 19.2.4 is installed alongside react 19.2.5.
3. The React team's own documentation states react and react-dom must be on the same version.
4. Conclusion: this PR is incomplete — it should have also bumped react-dom to 19.2.5.