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

chore(deps): update react monorepo to v19 (major) #476

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 6, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react (source) ^18.0.0 -> ^19.0.0 age adoption passing confidence
react-dom (source) ^18.0.0 -> ^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: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

@renovate renovate bot added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Dec 6, 2024
Copy link
Contributor Author

renovate bot commented Dec 6, 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: docs/package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @gatsbyjs/reach-router@2.0.1
npm warn Found: react@19.0.0
npm warn node_modules/react
npm warn   dev react@"^19.0.0" from the root project
npm warn   2 more (react-debounce-render, react-dom)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"18.x" from @gatsbyjs/reach-router@2.0.1
npm warn node_modules/@gatsbyjs/reach-router
npm warn   @gatsbyjs/reach-router@"^2.0.1" from gatsby@5.13.7
npm warn   node_modules/gatsby
npm warn   3 more (gatsby-link, gatsby-react-router-scroll, gatsby-script)
npm warn
npm warn Conflicting peer dependency: react@18.3.1
npm warn node_modules/react
npm warn   peer react@"18.x" from @gatsbyjs/reach-router@2.0.1
npm warn   node_modules/@gatsbyjs/reach-router
npm warn     @gatsbyjs/reach-router@"^2.0.1" from gatsby@5.13.7
npm warn     node_modules/gatsby
npm warn     3 more (gatsby-link, gatsby-react-router-scroll, gatsby-script)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @gatsbyjs/reach-router@2.0.1
npm warn Found: react-dom@19.0.0
npm warn node_modules/react-dom
npm warn   dev react-dom@"^19.0.0" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer react-dom@"18.x" from @gatsbyjs/reach-router@2.0.1
npm warn node_modules/@gatsbyjs/reach-router
npm warn   @gatsbyjs/reach-router@"^2.0.1" from gatsby@5.13.7
npm warn   node_modules/gatsby
npm warn   3 more (gatsby-link, gatsby-react-router-scroll, gatsby-script)
npm warn
npm warn Conflicting peer dependency: react-dom@18.3.1
npm warn node_modules/react-dom
npm warn   peer react-dom@"18.x" from @gatsbyjs/reach-router@2.0.1
npm warn   node_modules/@gatsbyjs/reach-router
npm warn     @gatsbyjs/reach-router@"^2.0.1" from gatsby@5.13.7
npm warn     node_modules/gatsby
npm warn     3 more (gatsby-link, gatsby-react-router-scroll, gatsby-script)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: gatsby@5.13.7
npm error Found: react@19.0.0
npm error node_modules/react
npm error   dev react@"^19.0.0" from the root project
npm error   peer overridden react@"^19.0.0" (was "^17.0.2") from react-debounce-render@8.0.2
npm error   node_modules/react-debounce-render
npm error     dev react-debounce-render@"^8.0.0" from the root project
npm error   1 more (react-dom)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0 || ^0.0.0" from gatsby@5.13.7
npm error node_modules/gatsby
npm error   dev gatsby@"^5.0.0" from the root project
npm error   peer gatsby@">3.0.0" from @gatsby-contrib/gatsby-plugin-elasticlunr-search@3.0.2
npm error   node_modules/@gatsby-contrib/gatsby-plugin-elasticlunr-search
npm error     dev @gatsby-contrib/gatsby-plugin-elasticlunr-search@"^3.0.0" from the root project
npm error   9 more (babel-plugin-remove-graphql-queries, ...)
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^18.0.0 || ^0.0.0" from gatsby@5.13.7
npm error   node_modules/gatsby
npm error     dev gatsby@"^5.0.0" from the root project
npm error     peer gatsby@">3.0.0" from @gatsby-contrib/gatsby-plugin-elasticlunr-search@3.0.2
npm error     node_modules/@gatsby-contrib/gatsby-plugin-elasticlunr-search
npm error       dev @gatsby-contrib/gatsby-plugin-elasticlunr-search@"^3.0.0" from the root project
npm error     9 more (babel-plugin-remove-graphql-queries, ...)
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/2024-12-06T21_42_09_892Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-06T21_42_09_892Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR
Projects
Status: 🆕 Triage
Development

Successfully merging this pull request may close these issues.

0 participants