chore(deps): update react monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/react (source)	18.2.79 -> 18.3.3
react (source)	18.2.0 -> 18.3.1
react-dom (source)	18.2.0 -> 18.3.1
react-test-renderer (source)	18.2.0 -> 18.3.1

---

Release Notes

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

facebook/react (react-test-renderer)

v18.3.1

Compare Source

v18.3.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate. View repository job log here.

[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: react-native@0.74.1
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   dev react@"18.3.1" from the root project
npm ERR!   peer react@"*" from @react-native/virtualized-lists@0.74.83
npm ERR!   node_modules/@react-native/virtualized-lists
npm ERR!     @react-native/virtualized-lists@"0.74.83" from react-native@0.74.1
npm ERR!   4 more (@testing-library/react-native, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"18.2.0" from react-native@0.74.1
npm ERR! node_modules/react-native
npm ERR!   dev react-native@"0.74.1" from the root project
npm ERR!   peer react-native@"*" from @react-native/virtualized-lists@0.74.83
npm ERR!   node_modules/@react-native/virtualized-lists
npm ERR!     @react-native/virtualized-lists@"0.74.83" from react-native@0.74.1
npm ERR!   1 more (@testing-library/react-native)
npm ERR! 
npm ERR! Conflicting peer dependency: react@18.2.0
npm ERR! node_modules/react
npm ERR!   peer react@"18.2.0" from react-native@0.74.1
npm ERR!   node_modules/react-native
npm ERR!     dev react-native@"0.74.1" from the root project
npm ERR!     peer react-native@"*" from @react-native/virtualized-lists@0.74.83
npm ERR!     node_modules/@react-native/virtualized-lists
npm ERR!       @react-native/virtualized-lists@"0.74.83" from react-native@0.74.1
npm ERR!     1 more (@testing-library/react-native)
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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-05T21_26_43_848Z-debug-0.log

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9dc2fcc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[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: react-native@0.74.1
npm ERR! Found: react@18.3.1
npm ERR! node_modules/react
npm ERR!   dev react@"18.3.1" from the root project
npm ERR!   peer react@"*" from @react-native/virtualized-lists@0.74.83
npm ERR!   node_modules/@react-native/virtualized-lists
npm ERR!     @react-native/virtualized-lists@"0.74.83" from react-native@0.74.1
npm ERR!   4 more (@testing-library/react-native, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"18.2.0" from react-native@0.74.1
npm ERR! node_modules/react-native
npm ERR!   dev react-native@"0.74.1" from the root project
npm ERR!   peer react-native@"*" from @react-native/virtualized-lists@0.74.83
npm ERR!   node_modules/@react-native/virtualized-lists
npm ERR!     @react-native/virtualized-lists@"0.74.83" from react-native@0.74.1
npm ERR!   1 more (@testing-library/react-native)
npm ERR! 
npm ERR! Conflicting peer dependency: react@18.2.0
npm ERR! node_modules/react
npm ERR!   peer react@"18.2.0" from react-native@0.74.1
npm ERR!   node_modules/react-native
npm ERR!     dev react-native@"0.74.1" from the root project
npm ERR!     peer react-native@"*" from @react-native/virtualized-lists@0.74.83
npm ERR!     node_modules/@react-native/virtualized-lists
npm ERR!       @react-native/virtualized-lists@"0.74.83" from react-native@0.74.1
npm ERR!     1 more (@testing-library/react-native)
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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-28T19_22_26_830Z-debug-0.log