Skip to content

fix(deps): update react monorepo to v19 (major) #402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) ^18 -> ^19.0.0 age adoption passing confidence
@types/react-dom (source) ^18 -> ^19.0.0 age adoption passing confidence
react (source) ^18 -> ^19.0.0 age adoption passing confidence
react-dom (source) ^18 -> ^19.0.0 age adoption passing confidence

Release Notes

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: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

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

Copy link
Contributor Author

renovate bot commented Dec 7, 2024

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/[email protected]
npm warn Found: [email protected]
npm warn node_modules/eslint
npm warn   dev eslint@"^9.0.0" from the root project
npm warn   7 more (@eslint-community/eslint-utils, eslint-config-next, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn node_modules/@typescript-eslint/eslint-plugin
npm warn   @typescript-eslint/eslint-plugin@"^5.4.2 || ^6.0.0 || ^7.0.0 || ^8.0.0" from [email protected]
npm warn   node_modules/eslint-config-next
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/eslint
npm warn   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn     @typescript-eslint/eslint-plugin@"^5.4.2 || ^6.0.0 || ^7.0.0 || ^8.0.0" from [email protected]
npm warn     node_modules/eslint-config-next
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/[email protected]
npm warn Found: [email protected]
npm warn node_modules/eslint
npm warn   dev eslint@"^9.0.0" from the root project
npm warn   7 more (@eslint-community/eslint-utils, eslint-config-next, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn node_modules/@typescript-eslint/parser
npm warn   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn   1 more (eslint-config-next)
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/eslint
npm warn   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn   node_modules/@typescript-eslint/parser
npm warn     peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm warn     node_modules/@typescript-eslint/eslint-plugin
npm warn     1 more (eslint-config-next)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/[email protected]
npm warn Found: [email protected]
npm warn node_modules/eslint
npm warn   dev eslint@"^9.0.0" from the root project
npm warn   7 more (@eslint-community/eslint-utils, eslint-config-next, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn node_modules/@typescript-eslint/type-utils
npm warn   @typescript-eslint/type-utils@"7.2.0" from @typescript-eslint/[email protected]
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/eslint
npm warn   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn   node_modules/@typescript-eslint/type-utils
npm warn     @typescript-eslint/type-utils@"7.2.0" from @typescript-eslint/[email protected]
npm warn     node_modules/@typescript-eslint/eslint-plugin
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/[email protected]
npm warn Found: [email protected]
npm warn node_modules/eslint
npm warn   dev eslint@"^9.0.0" from the root project
npm warn   7 more (@eslint-community/eslint-utils, eslint-config-next, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn node_modules/@typescript-eslint/utils
npm warn   @typescript-eslint/utils@"7.2.0" from @typescript-eslint/[email protected]
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn   1 more (@typescript-eslint/type-utils)
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/eslint
npm warn   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm warn   node_modules/@typescript-eslint/utils
npm warn     @typescript-eslint/utils@"7.2.0" from @typescript-eslint/[email protected]
npm warn     node_modules/@typescript-eslint/eslint-plugin
npm warn     1 more (@typescript-eslint/type-utils)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error   peer react@">=16.8.0" from @emotion/[email protected]
npm error   node_modules/@emotion/react
npm error     @emotion/react@"^11.11.1" from the root project
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/[email protected]
npm error     node_modules/@emotion/styled
npm error       @emotion/styled@"^11.11.0" from the root project
npm error       3 more (@mui/material, @mui/styled-engine, @mui/system)
npm error     3 more (@mui/material, @mui/styled-engine, @mui/system)
npm error   12 more (@emotion/styled, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.2.0" from [email protected]
npm error node_modules/next
npm error   peer next@"^12.2.5 || ^13 || ^14 || ^15" from [email protected]
npm error   node_modules/next-auth
npm error     next-auth@"^4.24.5" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^18.2.0" from [email protected]
npm error   node_modules/next
npm error     peer next@"^12.2.5 || ^13 || ^14 || ^15" from [email protected]
npm error     node_modules/next-auth
npm error       next-auth@"^4.24.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-04-25T01_26_37_271Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-25T01_26_37_271Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 7 times, most recently from 6a0100c to 6648aa8 Compare December 10, 2024 11:38
@renovate renovate bot changed the title chore(deps): update react monorepo to v19 (major) fix(deps): update react monorepo to v19 (major) Dec 10, 2024
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 11 times, most recently from 94a2341 to 05bc9d3 Compare December 17, 2024 17:54
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 14eeaea to 13f5edf Compare December 23, 2024 23:15
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from d1dfdf0 to 29f9e3c Compare December 29, 2024 15:04
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 7e87edf to 74c50fa Compare January 5, 2025 21:24
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 9 times, most recently from 0621298 to 715cfde Compare March 27, 2025 18:26
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 84ac1d8 to 3b81db6 Compare April 5, 2025 00:49
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 71142fa to 494c18e Compare April 10, 2025 00:31
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 97cf4a6 to 97467d7 Compare April 19, 2025 00:24
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from b803ee5 to add08b5 Compare April 24, 2025 18:26
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from add08b5 to ec7aba6 Compare April 25, 2025 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants