chore(deps): update jest monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/jest (source)	29.5.3 -> 29.5.14
jest (source)	29.6.2 -> 29.7.0

---

Release Notes

jestjs/jest (jest)

v29.7.0

Compare Source

Features

• [create-jest] Add npm init / yarn create initialiser for Jest projects (#​14465)
• [jest-validate] Allow deprecation warnings for unknown options (#​14499)

Fixes

• [jest-resolver] Replace unmatched capture groups in moduleNameMapper with empty string instead of undefined (#​14507)
• [jest-snapshot] Allow for strings as well as template literals in inline snapshots (#​14465)
• [@jest/test-sequencer] Calculate test runtime if perStats.duration is missing (#​14473)

Performance

• [@jest/create-cache-key-function] Cache access of NODE_ENV and BABEL_ENV (#​14455)

Chore & Maintenance

• [jest-cli] Move internal config initialisation logic to the create-jest package (#​14465)

New Contributors

• @​bawjensen made their first contribution in #​14465
• @​malaviya-parth made their first contribution in #​14467
• @​niklasholm made their first contribution in #​14507

Full Changelog: jestjs/jest@v29.6.4...v29.7.0

v29.6.4

Compare Source

Fixes

• [jest-core] Fix typo in scheduleAndRun performance marker (#​14434)
• [jest-environment-node] Make sure atob and btoa are writeable in Node 20 (#​14446)
• [jest-worker] Additional error wrapper for parentPort.postMessage to fix unhandled DataCloneError. (#​14437)

New Contributors

• @​stanleyume made their first contribution in #​14424
• @​dj-stormtrooper made their first contribution in #​14437
• @​thw0rted made their first contribution in #​14444

Full Changelog: jestjs/jest@v29.6.3...v29.6.4

v29.6.3

Compare Source

Fixes

• [expect, @​jest/expect-utils] ObjectContaining support symbol as key (#​14414)
• [expect] Remove @types/node from dependencies (#​14385)
• [jest-core] Use workers in watch mode by default to avoid crashes (#​14059 & #​14085).
• [jest-reporters] Update istanbul-lib-instrument dependency to v6. (#​14401)
• [jest-mock] Revert #​13692 as it was a breaking change (#​14429)
• [jest-mock] Revert #​13866 as it was a breaking change (#​14429)
• [jest-mock] Revert #​13867 as it was a breaking change (#​14429)
• [@jest/reporters] Marks Reporter's hooks as optional (#​14433)
• [jest-runtime] Fix dynamic ESM import module bug when loaded module through jest.isolateModulesAsync (#​14397)

Chore & Maintenance

• [jest-changed-files, jest-circus, jest-console, @​jest/core, @​jest/runtime, @​jest/transform] Use invariant and notEmpty from jest-util rather than own internal (#​14366)

New Contributors

• @​karlnorling made their first contribution in #​14401
• @​vinicinbgs made their first contribution in #​14388
• @​panteleevnikita made their first contribution in #​14433

Full Changelog: jestjs/jest@v29.6.2...v29.6.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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"29.7.0" from the root project
npm ERR!   peer jest@"^29.0.0" from [email protected]
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"29.1.0" 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 [email protected]
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: [email protected]
npm ERR! node_modules/jest
npm ERR!   peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from [email protected]
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-02-01T17_49_16_774Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-01T17_49_16_774Z-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: [email protected]
npm error Found: [email protected]
npm error node_modules/jest
npm error   dev jest@"29.7.0" from the root project
npm error   peer jest@"^29.0.0" from [email protected]
npm error   node_modules/ts-jest
npm error     dev ts-jest@"29.1.0" 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 [email protected]
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: [email protected]
npm error node_modules/jest
npm error   peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from [email protected]
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-10-21T23_36_50_478Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-21T23_36_50_478Z-debug-0.log