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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/jest (source)	29.5.14 -> 30.0.0
jest (source)	29.7.0 -> 30.2.0

---

Release Notes

jestjs/jest (jest)

v30.2.0

Compare Source

Chore & Maintenance

• [*] Update example repo for testing React Native projects (#​15832)
• [*] Update jest-watch-typeahead to v3 (#​15830)

v30.1.3

Compare Source

Fixes

• Fix unstable_mockModule with node: prefixed core modules.

v30.1.2

Compare Source

v30.1.1

Compare Source

Fixes

• [jest-snapshot-utils] Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#​15800)

v30.1.0

Compare Source

v30.0.5

Compare Source

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 - "every weekend" in timezone America/Los_Angeles, 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.

[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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/jest
npm error   dev jest@"30.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^29.0.0" from [email protected]
npm error node_modules/ts-jest
npm error   dev ts-jest@"29.3.2" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/jest
npm error   peer jest@"^29.0.0" from [email protected]
npm error   node_modules/ts-jest
npm error     dev ts-jest@"29.3.2" 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-10-25T09_29_19_130Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-25T09_29_19_130Z-debug-0.log