Skip to content

Update dependency jest-junit to v13.2.0#606

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/jest-junit-13.x
Open

Update dependency jest-junit to v13.2.0#606
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/jest-junit-13.x

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Apr 5, 2022

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

v13.2.0

Compare Source

Support monorepos better via filePathPrefix option by @​marvinroger - https://github.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

v13.1.0

Compare Source

Configurable test suite properties file location by @​JohanBrorson - https://github.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.


  • 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
Copy Markdown
Author

renovate Bot commented Apr 5, 2022

⚠ 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: search-query-enhancer/package-lock.json
npm notice 
npm notice New minor version of npm available! 8.5.0 -> 8.7.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.7.0>
npm notice Run `npm install -g npm@8.7.0` to update!
npm notice 
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-04-21T04_16_39_636Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/jest-junit-13.x branch from 96da87d to 16a39ec Compare April 21, 2022 04:16
@renovate renovate Bot changed the title Update dependency jest-junit to v13.1.0 Update dependency jest-junit to v13.2.0 Apr 21, 2022
@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Mar 23, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant