Update dependency jest to v29.4.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jest (source)	29.3.1 -> 29.4.1

---

Release Notes

facebook/jest

v29.4.1

Compare Source

Features

• [expect, jest-circus, @​jest/types] Implement numPassingAsserts of testResults to track the number of passing asserts in a test (#​13795)
• [jest-core] Add newlines to JSON output (#​13817)
• [@jest/reporters] Automatic log folding in GitHub Actions Reporter (#​13626)

Fixes

• [@jest/expect-utils] toMatchObject diffs should include Symbol properties (#​13810)
• [jest-runtime] Handle missing replaceProperty (#​13823)
• [@jest/types] Add partial support for done callbacks in typings of each (#​13756)

v29.4.0

Compare Source

Features

• [expect, @​jest/expect-utils] Support custom equality testers (#​13654)
• [jest-config, jest-worker] Use os.availableParallelism if available to calculate number of workers to spawn (#​13738)
• [@jest/globals, jest-mock] Add jest.replaceProperty() that replaces property value (#​13496)
• [jest-haste-map] ignore Sapling vcs directories (.sl/) (#​13674)
• [jest-resolve] Support subpath imports (#​13705, #​13723, #​13777)
• [jest-runtime] Add jest.isolateModulesAsync for scoped module initialization of asynchronous functions (#​13680)
• [jest-runtime] Add jest.isEnvironmentTornDown function (#​13741)
• [jest-test-result] Added skipped and focused status to FormattedTestResult (#​13700)
• [jest-transform] Support for asynchronous createTransformer (#​13762)

Fixes

• [jest-environment-node] Fix non-configurable globals (#​13687)
• [@jest/expect-utils] toMatchObject should handle Symbol properties (#​13639)
• [jest-mock] Fix mockReset and resetAllMocks undefined return value(#​13692)
• [jest-resolve] Add global paths to require.resolve.paths (#​13633)
• [jest-resolve] Correct node core module detection when using node: specifiers (#​13806)
• [jest-runtime] Support WASM files that import JS resources (#​13608)
• [jest-runtime] Use the scriptTransformer cache in jest-runner (#​13735)
• [jest-runtime] Enforce import assertions when importing JSON in ESM (#​12755 & #​13805)
• [jest-snapshot] Make sure to import babel outside of the sandbox (#​13694)
• [jest-transform] Ensure the correct configuration is passed to preprocessors specified multiple times in the transform option (#​13770)

Chore & Maintenance

• [@jest/fake-timers] Update @sinonjs/fake-timers (#​13612)
• [docs] Improve custom puppeteer example to prevent worker warnings (#​13619)

---

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 becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

[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: yarn.lock

error An unexpected error occurred: "Invalid value type 1621:0 in /mnt/renovate/gh/LLazyEmail/markdown-regex/yarn.lock".

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (29.4.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.