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/yauzl to v2.10.3 #635

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 25, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/yauzl (source) 2.9.2 -> 2.10.3 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
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
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @destinationstransfers/[email protected]
npm ERR! Found: [email protected]
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/[email protected]
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
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/[email protected]
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: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^6.6.0 || ^7.0.0" from @destinationstransfers/[email protected]
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/02c3e7/2998b1/cache/others/npm/_logs/2023-11-07T21_35_49_931Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/02c3e7/2998b1/cache/others/npm/_logs/2023-11-07T21_35_49_931Z-debug-0.log

@renovate renovate bot force-pushed the renovate/yauzl-2.x branch 3 times, most recently from 682320f to 73095ce Compare August 2, 2023 21:51
@renovate renovate bot changed the title Update dependency @types/yauzl to v2.10.0 Update dependency @types/yauzl to v2.10.1 Sep 25, 2023
@renovate renovate bot changed the title Update dependency @types/yauzl to v2.10.1 Update dependency @types/yauzl to v2.10.2 Oct 18, 2023
@renovate renovate bot changed the title Update dependency @types/yauzl to v2.10.2 Update dependency @types/yauzl to v2.10.3 Nov 7, 2023
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