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): lock file maintenance #2319

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 4, 2022

Mend Renovate

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), 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 Jul 4, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: lumitest@0.1.0
npm ERR! Found: react@18.1.0
npm ERR! node_modules/react
npm ERR!   react@"18.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4
npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"4.12.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-28T20_24_50_283Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-28T20_24_50_283Z-debug-0.log

@renovate renovate bot added the [type] chore label Jul 4, 2022
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 06511ff to b7606d2 Compare July 6, 2022 14:29
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from b7606d2 to ffeee71 Compare July 13, 2022 21:41
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from d6be90d to 381bdbf Compare July 27, 2022 23:51
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 381bdbf to f64dc92 Compare August 5, 2022 03:30
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 21 times, most recently from 376325e to 746bace Compare August 16, 2022 23:48
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from eab7faf to 667272b Compare April 11, 2023 00:18
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from f812ba1 to 212fbf3 Compare April 17, 2023 18:49
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 30330a8 to e55e24d Compare April 27, 2023 20:59
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 7 times, most recently from 8305a59 to 8db0f1a Compare May 4, 2023 22:53
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from 2c11d98 to 6befb1a Compare May 11, 2023 17:04
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 6befb1a to c720d6f Compare March 28, 2024 20:28
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from c720d6f to 2fb8754 Compare June 19, 2024 22:45
Copy link
Contributor Author

renovate bot commented Jun 19, 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 unable to resolve dependency tree
npm error
npm error While resolving: lumitest@0.1.0
npm error Found: react@18.1.0
npm error node_modules/react
npm error   react@"18.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4
npm error node_modules/@material-ui/core
npm error   @material-ui/core@"4.12.4" 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_42_14_664Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-19T22_42_14_664Z-debug-0.log

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