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 #2304

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 15, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 18.0.11 -> 18.3.3 age adoption passing confidence
@types/react (source) 17.0.53 -> 17.0.80 age adoption passing confidence
@types/react-dom (source) 18.0.5 -> 18.3.0 age adoption passing confidence
@types/react-dom (source) 17.0.19 -> 17.0.25 age adoption passing confidence
eslint-plugin-react-hooks (source) 4.6.0 -> 4.6.2 age adoption passing confidence
react (source) 18.1.0 -> 18.3.1 age adoption passing confidence
react-dom (source) 18.1.0 -> 18.3.1 age adoption passing confidence

Release Notes

facebook/react (eslint-plugin-react-hooks)

v4.6.2

Compare Source

v4.6.1

Compare Source

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)
facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

v18.2.0

Compare Source

React DOM
React DOM Server
Server Components (Experimental)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@renovate
Copy link
Contributor Author

renovate bot commented Jun 15, 2022

⚠ 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: reporter-client/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @material-ui/[email protected]
npm error Found: @types/[email protected]
npm error node_modules/@types/react
npm error   dev @types/react@"18.3.1" from the root project
npm error   peerOptional @types/react@"*" from @material-ui/[email protected]
npm error   node_modules/@material-ui/types
npm error     @material-ui/types@"5.1.0" from @material-ui/[email protected]
npm error     node_modules/@material-ui/core
npm error       @material-ui/core@"4.12.4" from the root project
npm error       1 more (@material-ui/icons)
npm error     @material-ui/types@"5.1.0" from @material-ui/[email protected]
npm error     node_modules/@material-ui/styles
npm error       @material-ui/styles@"^4.11.5" from the root project
npm error       1 more (@material-ui/core)
npm error   2 more (@types/react-transition-group, @types/react-dom)
npm error
npm error Could not resolve dependency:
npm error peerOptional @types/react@"^16.8.6 || ^17.0.0" from @material-ui/[email protected]
npm error node_modules/@material-ui/core
npm error   @material-ui/core@"4.12.4" from the root project
npm error   peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm error   node_modules/@material-ui/icons
npm error     @material-ui/icons@"4.11.3" from the root project
npm error
npm error Conflicting peer dependency: @types/[email protected]
npm error node_modules/@types/react
npm error   peerOptional @types/react@"^16.8.6 || ^17.0.0" from @material-ui/[email protected]
npm error   node_modules/@material-ui/core
npm error     @material-ui/core@"4.12.4" from the root project
npm error     peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm error     node_modules/@material-ui/icons
npm error       @material-ui/icons@"4.11.3" 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-04-26T22_48_20_733Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-26T22_48_20_733Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from f3956d4 to 253b87b Compare June 17, 2022 02:56
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from e58ef42 to 155aa6e Compare July 3, 2022 03:14
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from ef4b897 to 4445d26 Compare July 6, 2022 14:26
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 4445d26 to 1f6c579 Compare July 13, 2022 21:38
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from 892b70e to bcb7625 Compare July 27, 2022 23:47
@renovate renovate bot force-pushed the renovate/react-monorepo branch from bcb7625 to e345d58 Compare August 5, 2022 03:27
@renovate renovate bot force-pushed the renovate/react-monorepo branch 15 times, most recently from 5a81ccd to 41779d3 Compare August 14, 2022 23:25
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from 3280ee5 to 6798f5a Compare March 13, 2024 14:42
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from 6ab5c3f to 8edfd9e Compare March 18, 2024 16:54
@renovate renovate bot force-pushed the renovate/react-monorepo branch 7 times, most recently from 98b47db to 265597b Compare March 28, 2024 20:23
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from e879985 to 0cdd345 Compare April 9, 2024 01:51
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from f6fb92d to 56c16f7 Compare April 16, 2024 00:53
@renovate renovate bot force-pushed the renovate/react-monorepo branch 4 times, most recently from e31da79 to e613194 Compare April 26, 2024 22:48
@renovate renovate bot force-pushed the renovate/react-monorepo branch from e613194 to dad47be Compare May 11, 2024 13:39
Copy link
Contributor Author

renovate bot commented May 11, 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: reporter-client/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @material-ui/[email protected]
npm error Found: @types/[email protected]
npm error node_modules/@types/react
npm error   dev @types/react@"18.3.3" from the root project
npm error   peerOptional @types/react@"*" from @material-ui/[email protected]
npm error   node_modules/@material-ui/types
npm error     @material-ui/types@"5.1.0" from @material-ui/[email protected]
npm error     node_modules/@material-ui/core
npm error       @material-ui/core@"4.12.4" from the root project
npm error       1 more (@material-ui/icons)
npm error     @material-ui/types@"5.1.0" from @material-ui/[email protected]
npm error     node_modules/@material-ui/styles
npm error       @material-ui/styles@"^4.11.5" from the root project
npm error       1 more (@material-ui/core)
npm error   2 more (@types/react-transition-group, @types/react-dom)
npm error
npm error Could not resolve dependency:
npm error peerOptional @types/react@"^16.8.6 || ^17.0.0" from @material-ui/[email protected]
npm error node_modules/@material-ui/core
npm error   @material-ui/core@"4.12.4" from the root project
npm error   peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm error   node_modules/@material-ui/icons
npm error     @material-ui/icons@"4.11.3" from the root project
npm error
npm error Conflicting peer dependency: @types/[email protected]
npm error node_modules/@types/react
npm error   peerOptional @types/react@"^16.8.6 || ^17.0.0" from @material-ui/[email protected]
npm error   node_modules/@material-ui/core
npm error     @material-ui/core@"4.12.4" from the root project
npm error     peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm error     node_modules/@material-ui/icons
npm error       @material-ui/icons@"4.11.3" 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-06-19T22_40_46_264Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-19T22_40_46_264Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from dad47be to 2cc9cdf Compare May 23, 2024 21:02
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 2cc9cdf to 6ef4621 Compare June 19, 2024 22:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants