fix(deps): update react monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/react (source)	18.2.45 → 18.3.30
@types/react-dom (source)	18.2.18 → 18.3.7
react (source)	18.2.0 → 18.3.1
react-dom (source)	18.2.0 → 18.3.1

---

Release Notes

facebook/react (react)

v18.3.1

Compare Source

• Export act from react f1338f

v18.3.0

Compare Source

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React

• Allow writing to this.refs to support string ref codemod 909071
• Warn for deprecated findDOMNode outside StrictMode c3b283
• Warn for deprecated test-utils methods d4ea75
• Warn for deprecated Legacy Context outside StrictMode 415ee0
• Warn for deprecated string refs outside StrictMode #​25383
• Warn for deprecated defaultProps for function components #​25699
• Warn when spreading key #​25697
• Warn when using act from test-utils d4ea75

React DOM

• Warn for deprecated unmountComponentAtNode 8a015b
• Warn for deprecated renderToStaticNodeStream #​28874

---

Configuration

📅 Schedule: (UTC)

• 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 becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @newlevelup/remark-config@1.0.9
npm ERR! Found: remark@15.0.1
npm ERR! node_modules/remark
npm ERR!   dev remark@"15.0.1" from the root project
npm ERR!   remark@"^15.0.0" from remark-cli@12.0.1
npm ERR!   node_modules/remark-cli
npm ERR!     dev remark-cli@"12.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer remark@"14.0.3" from @newlevelup/remark-config@1.0.9
npm ERR! node_modules/@newlevelup/remark-config
npm ERR!   dev @newlevelup/remark-config@"1.0.9" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: remark@14.0.3
npm ERR! node_modules/remark
npm ERR!   peer remark@"14.0.3" from @newlevelup/remark-config@1.0.9
npm ERR!   node_modules/@newlevelup/remark-config
npm ERR!     dev @newlevelup/remark-config@"1.0.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /runner/cache/others/npm/_logs/2026-06-01T19_13_37_464Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-01T19_13_37_464Z-debug-0.log