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)
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 (^26.6.3 → ^27.2.5) · Repo · Changelog
Release Notes
27.2.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
v27.2.5
chore: update changelog for release
fix(reporters): verbose reporter should not buffer writes (#11054)
feat: warn when there are multiple configs (#11922)
chore(expect): expose default matchers (#11932)
fix(expect): `toThrow` and `toThrowError` typings (#11929)
fix(expect): make types better reflect reality (#11931)
fix: construct mather context for asymmetric matchers on demand (#11930)
fix: pass matcher context to asymmetric matchers (#11926)
chore: bump jest-junit
docs: fix a typo (#11921)
chore: tweak babel config (#11918)
fix(jest-haste-map): Add computeDependencies to cache path (#11916)
fix(cli): improve `--help` printout by removing defunct `--browser` option (#11914)
fix(types): mark deprecated configuration options as `@deprecated` (#11913)
Fix documentation of running ESM jest (#11717)
chore: update lockfile after release
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