Bump jest from 29.4.1 to 29.4.2 in /wrapper

[dependabot[bot]]

Bumps jest from 29.4.1 to 29.4.2.

Release notes

Sourced from jest's releases.

v29.4.2

Features

• [@jest/core] Instrument significant lifecycle events with performance.mark() (#13859)

Fixes

• [expect, @jest/expect] Provide type of actual as a generic argument to Matchers to allow better-typed extensions (#13848)
• [jest-circus] Added explicit mention of test failing because done() is not being called in error message (#13847)
• [jest-runtime] Handle CJS re-exports of node core modules from ESM (#13856)
• [jest-transform] Downgrade write-file-atomic to v4 (#13853)
• [jest-worker] Ignore IPC messages not intended for Jest (#13543)

Chore & Maintenance

• [*] make sure to exclude .eslintcache from published module (#13832)
• [docs] Cleanup incorrect links in CHANGELOG.md (#13857)

New Contributors

• @​benjaminjkraft made their first contribution in facebook/jest#13848
• @​LinusU made their first contribution in facebook/jest#13543
• @​SuperSodaSea made their first contribution in facebook/jest#13857
• @​kowalski made their first contribution in facebook/jest#13856

Full Changelog: https://github.com/facebook/jest/compare/v29.4.1...v29.4.2

Changelog

Sourced from jest's changelog.

29.4.2

Features

• [@jest/core] Instrument significant lifecycle events with performance.mark() (#13859)

Fixes

• [expect, @jest/expect] Provide type of actual as a generic argument to Matchers to allow better-typed extensions (#13848)
• [jest-circus] Added explicit mention of test failing because done() is not being called in error message (#13847)
• [jest-runtime] Handle CJS re-exports of node core modules from ESM (#13856)
• [jest-transform] Downgrade write-file-atomic to v4 (#13853)
• [jest-worker] Ignore IPC messages not intended for Jest (#13543)

Chore & Maintenance

• [*] make sure to exclude .eslintcache from published module (#13832)
• [docs] Cleanup incorrect links in CHANGELOG.md (#13857)

Commits

• f0fc92e v29.4.2
• bc7b20c chore: make sure to exclude .eslintcache from published module (#13832)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[bflad]

No longer applicable after #302

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[github-actions[bot]]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.