chore(deps): update jest monorepo to v30 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/jest (source)	^29.5.11 -> ^30.0.0
jest (source)	^29.7.0 -> ^30.0.0

---

Release Notes

jestjs/jest (jest)

v30.0.4

Compare Source

Features

• [expect] The Inverse type is now exported (#​15714)
• [expect] feat: support async functions in toBe (#​15704)

Fixes

• [jest] jest --onlyFailures --listTests now correctly lists only failed tests (#​15700)
• [jest-snapshot] Handle line endings in snapshots (#​15708)

v30.0.3

Compare Source

Fixes

• [jest-config] Fix ESM TS config loading in a CJS project (#​15694)

Features

• [jest-diff] Show non-printable control characters to diffs (#​15696)

v30.0.2

Compare Source

v30.0.1

Compare Source

v30.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Admin Frontend
• Backend external API console

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: doc-gen-service/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: ts-jest@29.2.5
npm error Found: jest@30.0.4
npm error node_modules/jest
npm error   dev jest@"^30.0.0" from the root project
npm error   peerOptional jest@"*" from eslint-plugin-jest@28.9.0
npm error   node_modules/eslint-plugin-jest
npm error     dev eslint-plugin-jest@"^28.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^29.0.0" from ts-jest@29.2.5
npm error node_modules/ts-jest
npm error   dev ts-jest@"^29.1.1" from the root project
npm error
npm error Conflicting peer dependency: jest@29.7.0
npm error node_modules/jest
npm error   peer jest@"^29.0.0" from ts-jest@29.2.5
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^29.1.1" 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-07-17T16_46_12_955Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-17T16_46_12_955Z-debug-0.log

File name: backend/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: jest-mock-extended@3.0.7
npm warn Found: jest@30.0.4
npm warn node_modules/jest
npm warn   dev jest@"^30.0.0" from the root project
npm warn   1 more (eslint-plugin-jest)
npm warn
npm warn Could not resolve dependency:
npm warn peer jest@"^24.0.0 || ^25.0.0 || ^26.0.0 || ^27.0.0 || ^28.0.0 || ^29.0.0" from jest-mock-extended@3.0.7
npm warn node_modules/jest-mock-extended
npm warn   jest-mock-extended@"^3.0.6" from prisma-mock@0.10.3
npm warn   node_modules/prisma-mock
npm warn
npm warn Conflicting peer dependency: jest@29.7.0
npm warn node_modules/jest
npm warn   peer jest@"^24.0.0 || ^25.0.0 || ^26.0.0 || ^27.0.0 || ^28.0.0 || ^29.0.0" from jest-mock-extended@3.0.7
npm warn   node_modules/jest-mock-extended
npm warn     jest-mock-extended@"^3.0.6" from prisma-mock@0.10.3
npm warn     node_modules/prisma-mock
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-jest@29.2.5
npm error Found: jest@30.0.4
npm error node_modules/jest
npm error   dev jest@"^30.0.0" from the root project
npm error   peerOptional jest@"*" from eslint-plugin-jest@28.9.0
npm error   node_modules/eslint-plugin-jest
npm error     dev eslint-plugin-jest@"^28.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^29.0.0" from ts-jest@29.2.5
npm error node_modules/ts-jest
npm error   dev ts-jest@"^29.1.1" from the root project
npm error
npm error Conflicting peer dependency: jest@29.7.0
npm error node_modules/jest
npm error   peer jest@"^29.0.0" from ts-jest@29.2.5
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^29.1.1" 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-07-17T16_46_24_605Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-17T16_46_24_605Z-debug-0.log

File name: backend-external/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: ts-jest@29.2.5
npm error Found: jest@30.0.4
npm error node_modules/jest
npm error   dev jest@"^30.0.0" from the root project
npm error   peerOptional jest@"*" from eslint-plugin-jest@28.9.0
npm error   node_modules/eslint-plugin-jest
npm error     dev eslint-plugin-jest@"^28.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^29.0.0" from ts-jest@29.2.5
npm error node_modules/ts-jest
npm error   dev ts-jest@"^29.1.1" from the root project
npm error
npm error Conflicting peer dependency: jest@29.7.0
npm error node_modules/jest
npm error   peer jest@"^29.0.0" from ts-jest@29.2.5
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^29.1.1" 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-07-17T16_46_31_279Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-17T16_46_31_279Z-debug-0.log

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 30.x releases. But if you manually upgrade to 30.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.