Update jest: 27.3.1 → 27.4.2 (minor) #281
Merged
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.3.1 → 27.4.2) · Repo · Changelog
Release Notes
27.4.2
27.4.1
27.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 50 commits:
v27.4.2
chore: update changelog for release
jest-worker: Avoid crash when "--max-old-space-size" inside process.execArgv (#12103)
chore: add `__typechecks__` directories to `.npmignore` (#12104)
chore: update lockfile after release
v27.4.1
chore: update changelog for release
jest-worker: Avoid crash when "--max-old-space-size" inside `process.execArgv` (#12097)
chore: move typecheck test files from root into packages (#12099)
fix(eslint): use eslint-import-resolver-typescript to fix import/no-unresolved (#12016)
chore: update lockfile after release
v27.4.0
chore: update changelog for release
docs: fix typos in CodeTransformation.md (#12034)
chore(CONTRIBUTING.md): recommend using node v16 (#12012)
jest-worker: Unable to customize thread execArgv with enableThreadWorkers (#12069)
fix(cli, config, docs): improve `mock` related cli messages, config template entries and documentation (#12047)
adding ts-jest mock util functions in jest-mock (#12089)
docs: Clarify setupFiles run order (#11641)
fix: avoid unhandled promise rejections when concurrent tests fail (#11987)
Enhancing the `toHaveProperty` matcher to support array selection (#12092)
Add `types` entry in export map (#12073)
docs: changed 'before' and 'after' ---> 'beforeAll' and 'afterAll' (#12065)
docs: alphabetize cli options (#11586)
Removed explicit type declarations (#12038)
README.md: HTTP => HTTPS (#12063)
chore(jest-runner): Add info regarding timers to forceExited message (#12083)
docs(jest-matcher-utils): fix link (#12072)
fix(jest-config): add missing slash dependency (#12080)
replaced `substr` with `substring` (#12066)
chore: fix PnP test by forcing older version of typescript
Remove cycle in printDiffs, diffLines and joinAlignedDiffs (#10818)
Do not reset global.document before CustomElement:disconnectedCallbac… (#11871)
fix(docs): add missing table of contents to The Jest Object documentation page (#12039)
Replaced module with namespace (#12018)
Correcting mockClear api docs (#12019)
Docs: docs/CodeTransformation.md (typo fix) (#12017)
fix: Incorrect detection of open ZLIB handles (#12022)
fix(jest-transform): improve runtime errors and warnings (#11998)
fix(docs): mention `processAsync` method as mandatory for `AsyncTransformer`s (#12013)
chore: force node v14 for jasmine build in CI
Set theme-color of docs to white (#12001)
feat(jest-diff, pretty-format): Add compareKeys option for sorting object keys (#11992)
feat(jest-core): support `testResultsProcessor` written in ESM (#12006)
jest-environment-jsdom: Set @types/jsdom in dependencies (#11999)
fix(expect): allow `expect.Matchers` generic with single value (#11986)
docs: move codeblock title to props & use line highlight (#11991)
docs/getting-started: Fix link to ParcelJS docs (#11988)
chore(ci): test on node 17 (#11983)
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