Update ts-jest 29.2.2 → 29.2.3 (patch) #196
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?
✳️ ts-jest (29.2.2 → 29.2.3) · Repo · Changelog
Release Notes
29.2.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
chore(release): 29.2.3
build(deps): Update dependency ejs to ^3.1.10
build(deps): Update dependency semver to v7.6.3
build(deps): Update dependency @types/node to v20.14.11
build(deps): Update dependency vite to ^5.3.4
build(deps): Update ESLint packages to ^7.16.1
build(deps-dev): bump braces from 3.0.2 to 3.0.3 in /examples/ts-only
build(deps): Update dependency @babel/core to ^7.24.9
build(deps): Update dependency @testing-library/dom to ^10.3.2
build(deps-dev): bump braces from 3.0.2 to 3.0.3 in /e2e/native-esm-ts
refactor(presets): maintain preset codes inside `src`
build(deps): Update babel monorepo to ^7.24.8
build(deps): Update dependency ts-jest to ^29.2.2
build(deps): Update dependency eslint-plugin-jsdoc to ^48.7.0
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