chore(deps): update dependency ts-jest to v29.3.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-jest (source)	29.1.0 -> 29.3.1

---

Release Notes

kulshekhar/ts-jest (ts-jest)

v29.3.1

Compare Source

Bug Fixes

• fix: allow isolatedModules mode to have ts.Program under Node16/Next (25157eb)
• fix: improve message for isolatedModules of ts-jest config (547eb6f)

v29.3.0

Compare Source

Features

• feat: support hybrid module values for isolatedModules: true (f372121)

Bug Fixes

• fix: set customConditions to undefined in TsCompiler (b091d70), closes #​4620

Code Refactoring

• refactor: remove manual version checker (89458fc)
• refactor: remove patching deps based on version checker (bac4c43)
• refactor: deprecate RawCompilerOptions interface (2b1b6cd)
• refactor: deprecate transform option isolatedModules (7dfef71)

v29.2.6

Compare Source

v29.2.5

Compare Source

v29.2.4

Compare Source

v29.2.3

Compare Source

v29.2.2

Compare Source

v29.2.1

Compare Source

v29.2.0

Compare Source

Bug Fixes

• fix: don't show warning message with Node16/NodeNext (99c4f49), closes #​4266

Features

• feat(cli): allow migrating cjs presets to transform config (22fb027)
• feat(presets): add util functions to create ESM presets (06f78ed), close #​4200
• feat(presets): add util functions to create CJS presets (f9cc3c0), close #​4200

Code refactoring

• refactor: replace lodash deps with native js implementation (40f1708)
• refactor: use TsJestTransformerOptions type everywhere possibly (7d001be)
• refactor(cli): use new preset util functions to initialize test config (c2b56ca)
• refactor(presets): use create preset util functions for cjs presets (922d6d0)
• test: switch react-app to use Vite (827c8ad)

v29.1.5

Compare Source

v29.1.4

Compare Source

v29.1.3

Compare Source

v29.1.2

Compare Source

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

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

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
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.3.1
npm error   node_modules/ts-jest
npm error     dev ts-jest@"29.3.1" 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 /runner/cache/others/npm/_logs/2025-03-31T18_57_44_806Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-31T18_57_44_806Z-debug-0.log