chore(deps): update react monorepo (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/react (source)	18.3.12 -> 19.0.7
@types/react-dom (source)	18.3.1 -> 19.0.3
eslint-plugin-react-hooks (source)	^4.4.0 -> ^5.0.0
react (source)	18.3.1 -> 19.0.0
react-dom (source)	18.3.1 -> 19.0.0

---

Release Notes

facebook/react (eslint-plugin-react-hooks)

v5.1.0

Compare Source

v5.0.0

Compare Source

• New Violations: Component names now need to start with an uppercase letter instead of a non-lowercase letter. This means _Button or _component are no longer valid. (@​kassens) in #​25162

• Consider dispatch from useActionState stable. (@​eps1lon in #​29665)
• Add support for ESLint v9. (@​eps1lon in #​28773)
• Accept as expression in callback. (@​StyleShit in #​28202)
• Accept as expressions in deps array. (@​StyleShit in #​28189)
• Treat React.use() the same as use(). (@​kassens in #​27769)
• Move use() lint to non-experimental. (@​kassens in #​27768)
• Support Flow as expressions. (@​cpojer in #​27590)
• Allow useEffect(fn, undefined). (@​kassens in #​27525)
• Disallow hooks in async functions. (@​acdlite in #​27045)
• Rename experimental useEvent to useEffectEvent. (@​sebmarkbage in #​25881)
• Lint for presence of useEvent functions in dependency lists. (@​poteto in #​25512)
• Check useEvent references instead. (@​poteto in #​25319)
• Update RulesOfHooks with useEvent rules. (@​poteto in #​25285)

v4.6.2

Compare Source

v4.6.1

Compare Source

v4.6.0

v4.5.0

• Fix false positive error with large number of branches. (@​scyron6 in #​24287)

facebook/react (react)

v19.0.0

Compare Source

facebook/react (react-dom)

v19.0.0

Compare Source

---

Configuration

📅 Schedule: 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 is behind base branch, 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: javascript/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @cucumber/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   dev react@"19.0.0" from the root project
npm ERR!   peer react@">=16.3" from @fortawesome/[email protected]
npm ERR!   node_modules/@fortawesome/react-fontawesome
npm ERR!     @fortawesome/react-fontawesome@"0.2.0" from @cucumber/[email protected]
npm ERR!     node_modules/@cucumber/react-components
npm ERR!       dev @cucumber/react-components@"22.3.0" from the root project
npm ERR!   4 more (react-error-boundary, react-markdown, use-debounce, react-dom)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"~18" from @cucumber/[email protected]
npm ERR! node_modules/@cucumber/react-components
npm ERR!   dev @cucumber/react-components@"22.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"~18" from @cucumber/[email protected]
npm ERR!   node_modules/@cucumber/react-components
npm ERR!     dev @cucumber/react-components@"22.3.0" 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! 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/2025-01-14T11_07_09_168Z-debug-0.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.