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) #37

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 2, 2025

This PR contains the following updates:

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

Copy link
Contributor Author

renovate bot commented Jan 2, 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: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @bcgov/[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.14.0" 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.14.0" from the root project
npm error       4 more (@mui/material, @mui/styled-engine, @mui/system, @mui/x-data-grid)
npm error     4 more (@mui/material, @mui/styled-engine, @mui/system, @mui/x-data-grid)
npm error   120 more (@emotion/styled, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.14.0 || ^17.0.0-rc.1 || ^18.0.0" from @bcgov/[email protected]
npm error node_modules/@bcgov/design-system-react-components
npm error   @bcgov/design-system-react-components@"^0.5.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.14.0 || ^17.0.0-rc.1 || ^18.0.0" from @bcgov/[email protected]
npm error   node_modules/@bcgov/design-system-react-components
npm error     @bcgov/design-system-react-components@"^0.5.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-02-01T03_43_46_375Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-01T03_43_46_375Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from ed4e4d8 to 6008085 Compare January 7, 2025 01:26
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 6008085 to 73f50c4 Compare January 7, 2025 21:49
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 73f50c4 to 7bd3a87 Compare January 7, 2025 23:23
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7bd3a87 to 654b3bf Compare January 8, 2025 04:44
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 654b3bf to 7efd747 Compare January 12, 2025 03:05
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 7efd747 to e7d8fa7 Compare January 16, 2025 09:42
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from e7d8fa7 to 3cfcf5f Compare January 22, 2025 01:50
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 3cfcf5f to a251a79 Compare January 22, 2025 02:13
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from a251a79 to 525357a Compare January 22, 2025 03:57
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 525357a to 826ebec Compare January 23, 2025 22:59
@renovate renovate bot force-pushed the renovate/major-react-monorepo branch from 826ebec to 296b240 Compare January 28, 2025 05:10
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