Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
depfu[bot]
commented
2 years ago
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ jest (^27.0.6 → ^29.0.2) · Repo · Changelog
Release Notes
29.0.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
v29.0.2chore: update changelog for releasedocs: use admonitions in Global APIs docs of v29 (#13198)fix(jest-mock): align behaviour and return type of `generateFromMetadata` method (#13207)fix: support `jest.resetModules` correctly in ESM (#13211)chore: remove some unneeded awaits from testschore: update `@microsoft/api-extractor`chore: update ts-eslint for TS 4.8 compatibility (#13197)docs: update `expect.extend` examples (#13195)docs: use admonitions in Global APIs docs (#13185)docs: correct grammar (#13194)Imported jest in mock (#13188)refactor(jest-config): mergeOptionWithPreset (#13190)chore: update to TypeScript 4.8 (#13177)docs: add missing admonition in Configuration docs (#13176)feat(jest-transform): expose `TransformerFactory` type (#13184)chore: update changelog for releaseDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands