Skip to content

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

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: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 23, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react (source) ^17.0.0 || ^18.0.0 -> ^17.0.0 || ^18.0.0 || ^19.0.0 age adoption passing confidence
react (source) ^18.3.1 -> ^19.0.0 age adoption passing confidence
react (source) ^18.0.0 -> ^19.0.0 age adoption passing confidence
react-dom (source) ^17.0.0 || ^18.0.0 -> ^17.0.0 || ^18.0.0 || ^19.0.0 age adoption passing confidence
react-dom (source) ^18.3.1 -> ^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 - "* 0-3 * * 1" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 Sep 23, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts 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: @edx/[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@">=16.3.2" from @restart/[email protected]
npm error   node_modules/@restart/context
npm error     @restart/context@"^2.1.4" from [email protected]
npm error     node_modules/react-bootstrap
npm error       react-bootstrap@"^1.6.5" from @openedx/[email protected]
npm error       node_modules/@openedx/paragon
npm error         dev @openedx/paragon@"^23.3.0" from the root project
npm error         1 more (@edx/frontend-platform)
npm error   24 more (@restart/hooks, @testing-library/react, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.9.0 || ^17.0.0 || ^18.0.0" from @edx/[email protected]
npm error node_modules/@edx/frontend-platform
npm error   dev @edx/frontend-platform@"^8.3.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.9.0 || ^17.0.0 || ^18.0.0" from @edx/[email protected]
npm error   node_modules/@edx/frontend-platform
npm error     dev @edx/frontend-platform@"^8.3.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 /runner/cache/others/npm/_logs/2025-04-16T15_38_32_182Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-16T15_38_32_182Z-debug-0.log

File name: example/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: @openedx/[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" from [email protected]
npm error   node_modules/react-router
npm error     react-router@"^6.22.3" from the root project
npm error     react-router@"6.26.2" from [email protected]
npm error     node_modules/react-router-dom
npm error       react-router-dom@"^6.22.3" from the root project
npm error   2 more (react-router-dom, react-dom)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.9.0 || ^17.0.0 || ^18.0.0" from @openedx/[email protected]
npm error node_modules/@openedx/frontend-build
npm error   dev @openedx/frontend-build@"^14.3.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.9.0 || ^17.0.0 || ^18.0.0" from @openedx/[email protected]
npm error   node_modules/@openedx/frontend-build
npm error     dev @openedx/frontend-build@"^14.3.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 /runner/cache/others/npm/_logs/2025-04-16T15_38_47_693Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-16T15_38_47_693Z-debug-0.log

File name: example-plugin-app/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: @openedx/[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" from [email protected]
npm error   node_modules/react-router
npm error     react-router@"6.26.2" from [email protected]
npm error     node_modules/react-router-dom
npm error       react-router-dom@"^6.22.1" from the root project
npm error   2 more (react-router-dom, react-dom)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.9.0 || ^17.0.0 || ^18.0.0" from @openedx/[email protected]
npm error node_modules/@openedx/frontend-build
npm error   @openedx/frontend-build@"^14.3.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.9.0 || ^17.0.0 || ^18.0.0" from @openedx/[email protected]
npm error   node_modules/@openedx/frontend-build
npm error     @openedx/frontend-build@"^14.3.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 /runner/cache/others/npm/_logs/2025-04-16T15_38_52_013Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-16T15_38_52_013Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 3173f85 to b178475 Compare November 1, 2024 15:08
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from b178475 to 5fc9ad2 Compare November 26, 2024 16:55
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 5fc9ad2 to f00ef0e Compare December 5, 2024 19:16
@renovate renovate bot changed the title chore(deps): update react monorepo to v18 (major) chore(deps): update react monorepo to v19 (major) Dec 5, 2024
@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 from f00ef0e to 9465e6d Compare December 19, 2024 16:28
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 9465e6d to 3b214a4 Compare January 6, 2025 15:36
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 3 times, most recently from 741a2fb to 66af0a4 Compare February 21, 2025 15:08
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch 2 times, most recently from 0cd3ac6 to 0263026 Compare March 12, 2025 18:33
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 0263026 to 933e70e Compare April 16, 2025 15:38
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