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 (major) #216

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 29, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-react-hooks (source) ^4.6.2 -> ^5.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
react-test-renderer (source) ^18.3.1 -> ^19.0.0 age adoption passing confidence

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
facebook/react (react)

v19.0.0

Compare Source

facebook/react (react-dom)

v19.0.0

Compare Source

facebook/react (react-test-renderer)

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.

👻 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.

Copy link
Contributor Author

renovate bot commented Nov 29, 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 ERESOLVE overriding peer dependency
npm warn While resolving: @gatsbyjs/[email protected]
npm warn Found: [email protected]
npm warn node_modules/react
npm warn   dev react@"^19.0.0" from the root project
npm warn   2 more (react-dom, react-test-renderer)
npm warn
npm warn Could not resolve dependency:
npm warn peer react@"18.x" from @gatsbyjs/[email protected]
npm warn node_modules/@gatsbyjs/reach-router
npm warn   @gatsbyjs/reach-router@"^2.0.1" from [email protected]
npm warn   node_modules/gatsby
npm warn   3 more (gatsby-link, gatsby-react-router-scroll, gatsby-script)
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/react
npm warn   peer react@"18.x" from @gatsbyjs/[email protected]
npm warn   node_modules/@gatsbyjs/reach-router
npm warn     @gatsbyjs/reach-router@"^2.0.1" from [email protected]
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/[email protected]
npm warn Found: [email protected]
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/[email protected]
npm warn node_modules/@gatsbyjs/reach-router
npm warn   @gatsbyjs/reach-router@"^2.0.1" from [email protected]
npm warn   node_modules/gatsby
npm warn   3 more (gatsby-link, gatsby-react-router-scroll, gatsby-script)
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/react-dom
npm warn   peer react-dom@"18.x" from @gatsbyjs/[email protected]
npm warn   node_modules/@gatsbyjs/reach-router
npm warn     @gatsbyjs/reach-router@"^2.0.1" from [email protected]
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: @testing-library/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   dev react@"^19.0.0" from the root project
npm error   peer react@"^19.0.0" from [email protected]
npm error   node_modules/react-dom
npm error     dev react-dom@"^19.0.0" from the root project
npm error   1 more (react-test-renderer)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @testing-library/[email protected]
npm error node_modules/@testing-library/react
npm error   dev @testing-library/react@"^16.0.1" 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 @testing-library/[email protected]
npm error   node_modules/@testing-library/react
npm error     dev @testing-library/react@"^16.0.1" 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/2024-12-05T22_24_37_038Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-05T22_24_37_038Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from b29988c to 118bd2a Compare December 5, 2024 22:24
@renovate renovate bot changed the title chore(deps): update dependency eslint-plugin-react-hooks to v5 chore(deps): update react monorepo (major) Dec 5, 2024
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