Update jest 23.2.0 → 29.6.3 (major) #221
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 (23.2.0 → 29.6.3) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 14 commits:
v29.6.3
chore: update changelog for release
chore: add `invariant` and `notEmpty` to `jest-util` (#14366)
fix: isolate esm async import bug (#14397)
Marks Reporter's hooks as optional (#14433)
Revert breaking changes to mocks (restoreAllMocks, spy changes) since 29.3.0 (#14429)
Archive docs versions 29.3 and below (#14425)
fix: symbol key could not be enum (#14414)
fix(deps): update dependency clsx to v2 (#14364)
fix(jest-core): don't use workers in watch mode if runInBand specified (#14085)
docs: incorrect specification to the method jest.replaceProperty (#14388)
fix(expect): remove @types/node from dependencies (#14385)
chore: update jest repo organisation in urls (#14413)
fix: update `istanbul-lib-instrument` to v6 (#14401)
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