chore(deps): update dependency ts-jest to v27.1.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ts-jest (source)	27.1.4 → 27.1.5

---

Release Notes

kulshekhar/ts-jest (ts-jest)

v27.1.5

Compare Source

Bug Fixes

• legacy invoke Babel processAsync for babel-jest in ESM mode instead of process (#​3430) (0d7356c)

Features

• presets: add presets for legacy mode (#​3465) (543b4ad)
• mark ConfigSet as legacy (#​3456) (a986729)
• mark TsCompiler and TsJestCompiler as legacy (#​3457) (0f2fe30)
• remove path-mapping AST transformer (#​3455) (f566869)
• set Jest peer dependencies to v28 (#​3454) (1e880ff)
• core: drop support for Node.js 10 (#​3332) (7a9aa61)
• core: remove mocked testing util (#​3333) (2d9017d)
• core: remove ts-jest/utils sub path export (#​3334) (9f253d3)
• mark TsJestTransformer as legacy (#​3451) (b090179)

BREAKING CHANGES

• path-mapping AST transformer is no longer shipped in ts-jest v28. Please use an alternative one like https://github.com/LeDDGroup/typescript-transform-paths instead.
• Any imports ts-jest/dist/compiler/ts-compiler should change to ts-jest/dist/legacy/compiler/ts-compiler
• Any imports ts-jest/dist/compiler/ts-jest-compiler should change to ts-jest/dist/legacy/compiler/ts-jest-compiler
• Any imports ts-jest/dist/config/config-set should change to ts-jest/dist/legacy/config/config-set
• Minimum support TypeScript version is now 4.3 since Jest 28 requires it.
• Jest 28 is required.
• core: Any imports ts-jest/utils should be replaced with ts-jest.
• core: Starting from Jest 27.4, mocked has been integrated into Jest repo.
• core: Support for Node.js v10 has been removed as Jest drops support for it.

27.1.5 (2022-05-17)

Bug Fixes

• transformers use Array.sort in hoisting transformer (#​3498) (e400a6e), fixes #​3476

27.1.4 (2022-03-24)

Bug Fixes

• compiler: revert #​3194 (#​3362) (2b7dffe), closes #​3272
• remove esbuild from peer dependency (#​3360) (8c8c1ca), closes #​3346
• support Babel config file with .cjs extension (#​3361) (5e5ac4a), closes #​3335

27.1.3 (2022-01-14)

Bug Fixes

• compiler: update memory cache for compiler using received file content (#​3194) (e4d9541)

27.1.2 (2021-12-15)

Bug Fixes

• stimulate esbuild type to avoid importing esbuild directly (#​3147) (9ace0a9)

27.1.1 (2021-12-07)

Bug Fixes

• bring back afterProcess hook (#​3132) (2b6b86e)
• make esbuild as optional peer dependency (#​3129) (20258de)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend"
• 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

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: root@undefined
npm ERR! Found: typescript@5.0.4
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"5.0.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=3.8 <5.0" from ts-jest@27.1.5
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"27.1.5" 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/c965a1/9a19e7/cache/others/npm/_logs/2023-07-22T03_17_43_809Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/c965a1/9a19e7/cache/others/npm/_logs/2023-07-22T03_17_43_809Z-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. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: root@undefined
npm error Found: typescript@5.0.4
npm error node_modules/typescript
npm error   dev typescript@"5.0.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=3.8 <5.0" from ts-jest@27.1.5
npm error node_modules/ts-jest
npm error   dev ts-jest@"27.1.5" 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/2026-04-08T14_57_57_833Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-08T14_57_57_833Z-debug-0.log