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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ts-jest (source)	29.4.11 → 29.4.12

---

Release Notes

kulshekhar/ts-jest (ts-jest)

v29.4.12

Compare Source

Features

• compiler: support TypeScript 7 projects through compatibility aliases (#​5386)

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• 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: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (872 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 9, reused 0, downloaded 0, added 0
Progress: resolved 10, reused 0, downloaded 0, added 0
Progress: resolved 14, reused 0, downloaded 0, added 0
Progress: resolved 15, reused 0, downloaded 0, added 0
Progress: resolved 17, reused 0, downloaded 1, added 0
[WARN] Request took 10154ms: https://registry.npmjs.org/@graphql-codegen%2Fschema-ast
Progress: resolved 18, reused 0, downloaded 1, added 0
[WARN] Request took 10629ms: https://registry.npmjs.org/@graphql-codegen%2Fplugin-helpers
[WARN] Request took 10578ms: https://registry.npmjs.org/@graphql-codegen%2Fplugin-helpers
[WARN] Request took 11311ms: https://registry.npmjs.org/@graphql-codegen%2Ftypescript
Progress: resolved 20, reused 0, downloaded 1, added 0
[WARN] Request took 11076ms: https://registry.npmjs.org/@graphql-codegen%2Ftypescript
[WARN] Request took 11204ms: https://registry.npmjs.org/@graphql-codegen%2Ftypescript-operations
[WARN] Request took 11607ms: https://registry.npmjs.org/@graphql-codegen%2Fvisitor-plugin-common
[WARN] Request took 12318ms: https://registry.npmjs.org/@graphql-codegen%2Fvisitor-plugin-common
Progress: resolved 21, reused 0, downloaded 1, added 0
[WARN] Request took 12309ms: https://registry.npmjs.org/@graphql-codegen%2Fcli
[WARN] Request took 12776ms: https://registry.npmjs.org/@graphql-codegen%2Fcli
Progress: resolved 72, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (872 entries in 14.9s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  @antfu/eslint-config@9.2.0 was published at 2026-07-22T03:43:03.000Z, within the minimumReleaseAge cutoff (2026-07-21T10:12:36.901Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
Progress: resolved 198, reused 0, downloaded 1, added 0