tinovyatkin / pass-js

Apple Wallet Passes generating library for Node.JS
MIT License
668 stars 81 forks source link

Update dependency jest-junit to v13.2.0 #614

Open renovate[bot] opened 2 years ago

renovate[bot] commented 2 years ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jest-junit 13.0.0 -> 13.2.0 age adoption passing confidence

Release Notes

jest-community/jest-junit (jest-junit) ### [`v13.2.0`](https://togithub.com/jest-community/jest-junit/releases/tag/v13.2.0) [Compare Source](https://togithub.com/jest-community/jest-junit/compare/v13.1.0...v13.2.0) Support monorepos better via filePathPrefix option by [@​marvinroger](https://togithub.com/marvinroger) - [https://github.com/jest-community/jest-junit/pull/209](https://togithub.com/jest-community/jest-junit/pull/209) Fix CI builds for windows and drop support for Node 10.x - [https://github.com/jest-community/jest-junit/pull/210](https://togithub.com/jest-community/jest-junit/pull/210) ### [`v13.1.0`](https://togithub.com/jest-community/jest-junit/releases/tag/v13.1.0) [Compare Source](https://togithub.com/jest-community/jest-junit/compare/v13.0.0...v13.1.0) Configurable test suite properties file location by [@​JohanBrorson](https://togithub.com/JohanBrorson) - [https://github.com/jest-community/jest-junit/pull/204](https://togithub.com/jest-community/jest-junit/pull/204)

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.



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

renovate[bot] commented 11 months ago

⚠ 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:

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_52_05_055Z-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_52_05_055Z-debug-0.log