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

chore(deps): update dependency ts-jest to v29.1.4 #452

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 30, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ts-jest (source) 29.1.0 -> 29.1.4 age adoption passing confidence

Release Notes

kulshekhar/ts-jest (ts-jest)

v29.1.4

Compare Source

Bug Fixes
Features

v29.1.3

Compare Source

Bug Fixes
  • add @jest/transform as an optional peer dependency (0ba7f86)
  • bring back Node 14 support (eda56a7)
Performance Improvements
  • remove ts resolved module cache file (4c88da5)

v29.1.2

Compare Source

Bug Fixes

v29.1.1

Compare Source

Security Fixes
  • bump semver to 7.5.3

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 Jun 30, 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: jest-react@0.14.0
npm ERR! Found: jest@29.6.2
npm ERR! node_modules/jest
npm ERR!   dev jest@"29.6.2" from the root project
npm ERR!   peer jest@"^29.0.0" from ts-jest@29.1.2
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"29.1.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm ERR! node_modules/jest-react
npm ERR!   dev jest-react@"0.14.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: jest@25.5.4
npm ERR! node_modules/jest
npm ERR!   peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm ERR!   node_modules/jest-react
npm ERR!     dev jest-react@"0.14.0" 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/renovate/cache/others/npm/_logs/2024-01-22T12_48_06_660Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-01-22T12_48_06_660Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update dependency ts-jest to v29.1.1 chore(deps): update dependency ts-jest to v29.1.2 Jan 22, 2024
Copy link
Contributor Author

renovate bot commented May 21, 2024

⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: jest-react@0.14.0
npm error Found: jest@29.6.2
npm error node_modules/jest
npm error   dev jest@"29.6.2" from the root project
npm error   peer jest@"^29.0.0" from ts-jest@29.1.4
npm error   node_modules/ts-jest
npm error     dev ts-jest@"29.1.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm error node_modules/jest-react
npm error   dev jest-react@"0.14.0" from the root project
npm error
npm error Conflicting peer dependency: jest@25.5.4
npm error node_modules/jest
npm error   peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm error   node_modules/jest-react
npm error     dev jest-react@"0.14.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-28T07_13_45_535Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-28T07_13_45_535Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update dependency ts-jest to v29.1.2 chore(deps): update dependency ts-jest to v29.1.3 May 21, 2024
@renovate renovate bot changed the title chore(deps): update dependency ts-jest to v29.1.3 chore(deps): update dependency ts-jest to v29.1.4 May 28, 2024
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.

None yet

0 participants