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

Update react monorepo to v19 (major) #66

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 6, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) ^18.3.13 -> ^19.0.0 age adoption passing confidence
@types/react-dom (source) ^18.3.1 -> ^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 - "* 0-3 * * 1" (UTC), 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 Jan 6, 2025

⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @tanstack/[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 @dnd-kit/[email protected]
npm error   node_modules/@dnd-kit/accessibility
npm error     @dnd-kit/accessibility@"^3.1.1" from @dnd-kit/[email protected]
npm error     node_modules/@dnd-kit/core
npm error       @dnd-kit/core@"^6.3.0" from the root project
npm error       2 more (@dnd-kit/modifiers, @dnd-kit/sortable)
npm error   52 more (@dnd-kit/core, @dnd-kit/modifiers, @dnd-kit/sortable, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @tanstack/[email protected]
npm error node_modules/@tanstack/react-query
npm error   peer @tanstack/react-query@"^4.18.0" from @trpc/[email protected]
npm error   node_modules/@trpc/next
npm error     @trpc/next@"^10.45.2" from the root project
npm error   peer @tanstack/react-query@"^4.18.0" from @trpc/[email protected]
npm error   node_modules/@trpc/react-query
npm error     @trpc/react-query@"^10.45.2" from the root project
npm error     1 more (@trpc/next)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @tanstack/[email protected]
npm error   node_modules/@tanstack/react-query
npm error     peer @tanstack/react-query@"^4.18.0" from @trpc/[email protected]
npm error     node_modules/@trpc/next
npm error       @trpc/next@"^10.45.2" from the root project
npm error     peer @tanstack/react-query@"^4.18.0" from @trpc/[email protected]
npm error     node_modules/@trpc/react-query
npm error       @trpc/react-query@"^10.45.2" from the root project
npm error       1 more (@trpc/next)
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-03-25T02_21_26_512Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-25T02_21_26_512Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from fdcc857 to 12c168e Compare January 13, 2025 05:16
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from afdb65e to ce1ffaa Compare January 20, 2025 05:23
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from dd521ed to 30c6915 Compare January 26, 2025 13:03
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from e20284f to b66f630 Compare February 10, 2025 04:45
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 107c706 to feb41b5 Compare February 17, 2025 06:29
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 7e85465 to 2426114 Compare February 24, 2025 05:27
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 5 times, most recently from 6f63c20 to c8d7855 Compare March 3, 2025 11:49
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 251aa35 to fc22473 Compare March 10, 2025 11:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 2b7f1b1 to e7563b9 Compare March 21, 2025 22:51
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from e7563b9 to 6eefd33 Compare March 25, 2025 02: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.

0 participants