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

Update dependency @types/node to v12.20.55 #573

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 13, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 12.20.29 -> 12.20.55 age adoption passing confidence

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency @types/node to v12.20.31 Update dependency @types/node to v12.20.32 Oct 13, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch 2 times, most recently from 4a62bc4 to e7cf147 Compare October 13, 2021 23:38
@renovate renovate bot changed the title Update dependency @types/node to v12.20.32 Update dependency @types/node to v12.20.33 Oct 13, 2021
@renovate renovate bot force-pushed the renovate/node-12.x branch 4 times, most recently from fc1fc59 to 0eb6119 Compare October 18, 2021 16:43
@renovate renovate bot changed the title Update dependency @types/node to v12.20.33 Update dependency @types/node to v12.20.34 Oct 22, 2021
@renovate renovate bot changed the title Update dependency @types/node to v12.20.34 Update dependency @types/node to v12.20.35 Oct 25, 2021
@renovate renovate bot changed the title Update dependency @types/node to v12.20.35 Update dependency @types/node to v12.20.36 Oct 26, 2021
@renovate renovate bot changed the title Update dependency @types/node to v12.20.36 Update dependency @types/node to v12.20.37 Nov 8, 2021
@renovate renovate bot changed the title Update dependency @types/node to v12.20.37 Update dependency @types/node to v12.20.38 Dec 20, 2021
@renovate renovate bot changed the title Update dependency @types/node to v12.20.38 Update dependency @types/node to v12.20.39 Dec 26, 2021
@renovate renovate bot changed the title Update dependency @types/node to v12.20.39 Update dependency @types/node to v12.20.46 Mar 7, 2022
@renovate renovate bot changed the title Update dependency @types/node to v12.20.46 Update dependency @types/node to v12.20.47 Mar 8, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch 4 times, most recently from 410f4e1 to d9f5bc1 Compare March 10, 2022 06:34
@renovate renovate bot force-pushed the renovate/node-12.x branch 5 times, most recently from 2465860 to 469609d Compare March 18, 2022 11:52
@renovate renovate bot force-pushed the renovate/node-12.x branch 4 times, most recently from d8910a9 to 45e78b9 Compare April 1, 2022 21:17
@renovate renovate bot changed the title Update dependency @types/node to v12.20.47 Update dependency @types/node to v12.20.48 Apr 14, 2022
@renovate renovate bot changed the title Update dependency @types/node to v12.20.48 Update dependency @types/node to v12.20.49 Apr 25, 2022
@renovate renovate bot changed the title Update dependency @types/node to v12.20.49 Update dependency @types/node to v12.20.50 Apr 26, 2022
@renovate renovate bot changed the title Update dependency @types/node to v12.20.50 Update dependency @types/node to v12.20.51 May 10, 2022
@renovate renovate bot changed the title Update dependency @types/node to v12.20.51 Update dependency @types/node to v12.20.52 May 12, 2022
@renovate renovate bot changed the title Update dependency @types/node to v12.20.52 Update dependency @types/node to v12.20.55 Jun 18, 2022
@renovate renovate bot force-pushed the renovate/node-12.x branch 2 times, most recently from 6edc2ce to 52fd3be Compare October 22, 2022 18:54
@renovate
Copy link
Contributor Author

renovate bot commented Jul 29, 2023

⚠ 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: package-lock.json
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @destinationstransfers/eslint-plugin@2.9.190
npm ERR! Found: eslint@8.46.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"8.46.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from eslint@8.46.0
npm ERR!   13 more (@typescript-eslint/experimental-utils, babel-eslint, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^6.6.0 || ^7.0.0" from @destinationstransfers/eslint-plugin@2.9.190
npm ERR! node_modules/@destinationstransfers/eslint-plugin
npm ERR!   dev @destinationstransfers/eslint-plugin@"2.9.190" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^6.6.0 || ^7.0.0" from @destinationstransfers/eslint-plugin@2.9.190
npm ERR!   node_modules/@destinationstransfers/eslint-plugin
npm ERR!     dev @destinationstransfers/eslint-plugin@"2.9.190" 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/worker/43459d/1dc09a/cache/others/npm/_logs/2023-08-02T21_51_10_250Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/43459d/1dc09a/cache/others/npm/_logs/2023-08-02T21_51_10_250Z-debug-0.log

@renovate renovate bot force-pushed the renovate/node-12.x branch 2 times, most recently from 4648270 to d90b91f Compare August 2, 2023 20:38
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