Skip to content
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

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

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 12, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) ^18.3.3 -> ^19.0.0 age adoption passing confidence
@types/react-dom (source) ^18.3.0 -> ^19.0.0 age adoption passing confidence
react (source) ^18.3.1 -> ^19.0.0 age adoption passing confidence
react-dom (source) ^18.3.1 -> ^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.


Thanks for the PR!

Deployments, as required, will be available below:

Please create PRs in draft mode. Mark as ready to enable:

After merge, new images are deployed in:

@renovate renovate bot enabled auto-merge (squash) December 12, 2024 20:48
Copy link
Contributor Author

renovate bot commented Dec 12, 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: frontend/package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @react-leaflet/[email protected]
npm warn Found: [email protected]
npm warn node_modules/react
npm warn   react@"^19.0.0" from the root project
npm warn   22 more (@emotion/react, @emotion/styled, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"^18.0.0" from @react-leaflet/[email protected]
npm warn node_modules/@react-leaflet/core
npm warn   @react-leaflet/core@"^2.1.0" from [email protected]
npm warn   node_modules/react-leaflet
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/react
npm warn   peer react@"^18.0.0" from @react-leaflet/[email protected]
npm warn   node_modules/@react-leaflet/core
npm warn     @react-leaflet/core@"^2.1.0" from [email protected]
npm warn     node_modules/react-leaflet
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @react-leaflet/[email protected]
npm warn Found: [email protected]
npm warn node_modules/react-dom
npm warn   react-dom@"^19.0.0" from the root project
npm warn   6 more (@mui/material, @testing-library/react, @mui/material, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer react-dom@"^18.0.0" from @react-leaflet/[email protected]
npm warn node_modules/@react-leaflet/core
npm warn   @react-leaflet/core@"^2.1.0" from [email protected]
npm warn   node_modules/react-leaflet
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/react-dom
npm warn   peer react-dom@"^18.0.0" from @react-leaflet/[email protected]
npm warn   node_modules/@react-leaflet/core
npm warn     @react-leaflet/core@"^2.1.0" from [email protected]
npm warn     node_modules/react-leaflet
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.4" 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.5" from the root project
npm error       7 more (@mui/material, @mui/styled-engine, @mui/system, ...)
npm error     7 more (@mui/material, @mui/styled-engine, @mui/system, ...)
npm error   21 more (@emotion/styled, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from [email protected]
npm error node_modules/react-leaflet
npm error   react-leaflet@"^4.2.1" from the root project
npm error   peer react-leaflet@"^4.0.0" from [email protected]
npm error   node_modules/react-leaflet-cluster
npm error     react-leaflet-cluster@"^2.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^18.0.0" from [email protected]
npm error   node_modules/react-leaflet
npm error     react-leaflet@"^4.2.1" from the root project
npm error     peer react-leaflet@"^4.0.0" from [email protected]
npm error     node_modules/react-leaflet-cluster
npm error       react-leaflet-cluster@"^2.1.0" 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 /tmp/renovate/cache/others/npm/_logs/2025-01-24T01_40_47_839Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-24T01_40_47_839Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 82bd8af to d6f9cc7 Compare December 24, 2024 22:30
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 0074952 to e9c2b74 Compare January 7, 2025 19:41
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 08ba910 to f6cda11 Compare January 15, 2025 20:56
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 6 times, most recently from 1d4ac4f to e439179 Compare January 23, 2025 21:01
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from e439179 to 29bbda3 Compare January 24, 2025 01:40
@mishraomp mishraomp closed this Jan 27, 2025
auto-merge was automatically disabled January 27, 2025 21:20

Pull request was closed

Copy link
Contributor Author

renovate bot commented Jan 27, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 19.x releases. But if you manually upgrade to 19.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/major-react-monorepo branch January 27, 2025 21:21
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.

1 participant