Update dependency ts-jest to v27.1.5

renovate[bot] commented 1 year ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-jest (source)	`27.1.4` -> `27.1.5`

Release Notes

kulshekhar/ts-jest (ts-jest)

### [`v27.1.5`](https://togithub.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md#2715-2022-05-17) [Compare Source](https://togithub.com/kulshekhar/ts-jest/compare/v27.1.4...v27.1.5) ##### Bug Fixes - **transformers** use `Array.sort` in hoisting transformer ([#3498](https://togithub.com/kulshekhar/ts-jest/pull/3498)) ([e400a6e](https://togithub.com/kulshekhar/ts-jest/commit/e400a6ec0e4706f606ae9b1e2897b0bb1cff6343)), fixes [#3476](https://togithub.com/kulshekhar/ts-jest/issues/3476)

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

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 @typescript-eslint/utils@5.60.1
npm ERR!     node_modules/@typescript-eslint/utils
npm ERR!       @typescript-eslint/utils@"5.60.1" from @typescript-eslint/eslint-plugin@5.60.1
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         dev @typescript-eslint/eslint-plugin@"5.60.1" from the root project
npm ERR!       1 more (@typescript-eslint/type-utils)
npm ERR!     @eslint-community/eslint-utils@"^4.2.0" from eslint@8.46.0
npm ERR!   15 more (@typescript-eslint/eslint-plugin, ...)
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/1b2a2f/f85d29/cache/others/npm/_logs/2023-08-02T20_38_19_696Z-eresolve-report.txt

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

renovate[bot] commented 11 months ago

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.

tinovyatkin / pass-js