Update eslint-plugin-jest 26.1.5 → 28.2.0 (major) #163
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
✳️ eslint-plugin-jest (26.1.5 → 28.2.0) · 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 more commits than we can show here.
Sorry, we couldn't find anything useful about this release.
Release Notes
4.3.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
4.3.4replace deprecated String.prototype.substr() (#876)add section about configuring JS console to show debug messages (#866)Release Notes
3.4.3
3.4.2
3.4.1
3.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 23 commits:
chore: release 3.4.3 (#57)chore: Add back add-to-triage (#59)chore: standardize npm script names (#55)chore: update `typedef` in build keys template (#58)chore: Remove add-to-triage (#56)chore: release 3.4.2 (#51)chore: Add PRs to triage (#54)ci: generate provenance statements when release (#53)docs: remove `release` script reference from README (#52)docs: fix spelling mistakes (#50)chore: release 3.4.1 (#49)chore: set up release-please (#48)fix: correct types for node16 resolution (#47)ci: run tests on Node.js v20 (#45)3.4.0Build: changelog update for 3.4.0fix: remove useless sourcemap url (fixes #43) (#44)chore: add triage action (#42)ci: add Node v19 (#41)chore: update github actions and add funding field (#40)build: add node v18 (#39)feat: add `JSXSpreadChild` and tool to build keys out of AST definitions (#36)docs: update badges (#37)🆕 @eslint-community/eslint-utils (added, 4.4.0)
🆕 @types/semver (added, 7.5.8)
🆕 ts-api-utils (added, 1.3.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