Update jest: 27.0.6 → 27.1.1 (minor) #12
Open
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ jest (27.0.6 → 27.1.1) · Repo · Changelog
Release Notes
27.1.1
27.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 44 commits:
v27.1.1
chore: update changelog for release
fix(resolver): support node prefix from ESM (#11817)
chore: bump version of CircleCI orb (#11822)
chore: get rid of warnings when running react tests (#11821)
feat(runtime): add minimal support for mocking ESM (#11818)
chore: update lockfiles after yarn update
chore: fix PnP compat test
chore: update yarn
Export PrettyFormatOptions type (#11801)
docs: update transformer documentation to include async transforms (#11716)
chore: remove non-existent release from changelog
chore: roll new website version
chore: update lockfile after publish
v27.1.0
chore: update changelog for release
chore(ci): use "latest" version of the OSes on Azure Pipelines (#11793)
feat(resolver): support `node:` prefix when loading core modules (#11331)
[jest-each] Relaxed the validation to allow multibyte characters in headings (#11575)
[jest-haste-map] Use more optimal suffix-set format (#11784)
chore: fix typo in examples (#11788)
fix(jest-types): compat with @types/node v16 (#11645)
chore: fix PnP test by forcing older version of typescript
chore: replace issue templates with forms (#11772)
fix: support userAgent option for jsdom environment (#11773)
Adds options for configuring the snapshot and inline snapshot serializers (#11654)
Add testExecError to testResultsProcessor docs (#11670)
chore: refresh lockfile (#11760)
chore(deps): bump dessant/lock-threads from 2.1.1 to 2.1.2 (#11762)
docs: update ECMAScript Modules file extension examples (#11615)
fix(resolver): add dependency on `jest-haste-map` (#11759)
chore: add workspaces yarn plugin
fix: spyOn should not rely on hasOwnProperty from the spied object (#11721)
docs: add partials mocking guide (#11537)
docs: fix broken links to jest documentation (#11582)
Expose `getSummary` from `jest-reporters.utils` (#11695)
Fix links to type definition in Jest-Circus README.md (#11711)
chore: use builtin dep caching in actions/setup-node (#11747)
fix(jest-environment-node): Add Event and EventTarget to node global (#11727)
docs: fix typo in blog Jest 25 (#11699)
chore(deps): bump dessant/lock-threads from 2.0.3 to 2.1.1 (#11655)
Update expect.assertions documentation (#11621)
chore: update lockfile after publish
chore: update changelog for release
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/
.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