tfelder-deloitte / SecurityTesting

Other
0 stars 0 forks source link

Update dependency jest-junit to v14 - autoclosed #610

Closed renovate[bot] closed 1 year 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 -> 14.0.1 age adoption passing confidence

Release Notes

jest-community/jest-junit ### [`v14.0.1`](https://togithub.com/jest-community/jest-junit/releases/tag/v14.0.1) [Compare Source](https://togithub.com/jest-community/jest-junit/compare/v14.0.0...v14.0.1) Prevent unnecessary duplicate test cases by [@​azzlack](https://togithub.com/azzlack) - [https://github.com/jest-community/jest-junit/pull/221](https://togithub.com/jest-community/jest-junit/pull/221) ### [`v14.0.0`](https://togithub.com/jest-community/jest-junit/releases/tag/v14.0.0) [Compare Source](https://togithub.com/jest-community/jest-junit/compare/v13.2.0...v14.0.0) - Fix getOptions support for Windows machines [#​215](https://togithub.com/jest-community/jest-junit/issues/215) by [@​mastrzyz](https://togithub.com/mastrzyz) - Failures in Test hooks like "AfterAll" now get shown in the Junit Results [#​214](https://togithub.com/jest-community/jest-junit/issues/214) by [@​mastrzyz](https://togithub.com/mastrzyz) ### [`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: Disabled due to failing status checks.

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 2 years 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: search-query-enhancer/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: awesome-typescript-loader@5.2.1
npm ERR! Found: typescript@4.3.5
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"4.3.5" from the root project
npm ERR!   peer typescript@">=3.8 <5.0" from ts-jest@27.1.3
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"27.1.3" from the root project
npm ERR!   2 more (tslint, tsutils)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"^2.7 || ^3" from awesome-typescript-loader@5.2.1
npm ERR! node_modules/awesome-typescript-loader
npm ERR!   dev awesome-typescript-loader@"5.2.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@3.9.10
npm ERR! node_modules/typescript
npm ERR!   peer typescript@"^2.7 || ^3" from awesome-typescript-loader@5.2.1
npm ERR!   node_modules/awesome-typescript-loader
npm ERR!     dev awesome-typescript-loader@"5.2.1" 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/2022-09-25T19_31_41_728Z-debug-0.log