This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
Upgrade jest: 24.1.0 → 29.4.3 (major) #89
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 (24.1.0 → 29.4.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 30 commits:
v29.4.3chore: update changelog for releaseUpdate toThrow() to be able to use Error.cause (#13606)fix: added inherited string keys check on `subsetEquality` method (#13824)Revert import assertions (#13911)feat: allow to use workerIdleMemoryLimit with only 1 worker or runInBand option (#13846)docs: add missing admonitions in configuration page v29 (#13908)feat(jest-message-util): improve detection of error causes (#13912)fix(jest-mock): do not restore mocks when `jest.resetAllMocks()` is called (#13866)chore: do not use built version of circus in unit test (#13907)chore: do not use deep imports in unit tests (#13905)docs: clean up Getting Started page (#13896)chore: retry cleanup in e2e tests (#13900)docs: Fix typos in documentation for custom equality testers (#13878)docs: add few missing admonitions to the CLI Options page (#13894)[jest-config] simplify filter-reduce (#13899)jest-each: simplify interpolation (#13898)docs: add few missing admonitions to the Expect API page (#13892)docs: use `npm2yarn` in all versions of Getting Started page (#13893)docs: add a note on difference between `toEqual` and `toStrictEqual` (#13891)chore: retry yarn install in e2e tests (#13890)fix(jest-mock): prevent `mockImplementationOnce` bleeding into `withImplementation` (#13888)refactor(jest-mock): remove unused `specificReturnValues` property (#13889)chore(e2e): attempt to log better errors when running commands (#13881)Update copyrights with Meta Platforms, restore original license in Jasmine fork (#13879)feat(jest-message-util): add support for error causes (#13868)fix(jest-mock): clear mock when `jest.restoreAllMocks()` is called (#13867)docs: fix a mistake introduced in #13870 (#13872)docs: few more admonitions for Mock Functions page (#13870)chore: fix link in changelogDepfu 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