Skip to content

chore(deps): lock file maintenance #693

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

Merged
merged 3 commits into from
Oct 15, 2021
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 14, 2021

WhiteSource 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: "before 5am on monday" (UTC).

🚦 Automerge: Disabled due to failing status checks.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

👻 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 has been generated by WhiteSource Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 14, 2021

⚠ 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 check 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @netlify/plugin-nextjs@4.0.0-beta.0
npm ERR! Found: next@11.1.3-canary.71
npm ERR! node_modules/next
npm ERR!   next@"^11.1.3-canary.65" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer next@">=10.2.0" from eslint-config-next@11.1.2
npm ERR! node_modules/eslint-config-next
npm ERR!   dev eslint-config-next@"^11.0.0" 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! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-10-15T09_11_02_793Z-debug.log

@github-actions github-actions bot added the type: chore work needed to keep the product and development running smoothly label Oct 14, 2021
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 62051f7 to 06d6dce Compare October 15, 2021 08:03
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 06d6dce to 7afb372 Compare October 15, 2021 09:11
@ascorbic ascorbic merged commit 8d982d5 into main Oct 15, 2021
@ascorbic ascorbic deleted the renovate/lock-file-maintenance branch October 15, 2021 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: chore work needed to keep the product and development running smoothly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants