Update eslint-plugin-testing-library 5.11.1 → 6.1.0 (major) #151
Conversation
This file contains hidden or 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}
✅ Deploy Preview for firefox-devtools-react-contextmenu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
testing-library/eslint-plugin-testing-library#812 is still not fixed (but a PR is on its way!), so I'm closing this update for now. Hopefully next update will have the fix! |
depfu
bot
deleted the
depfu/update/yarn/eslint-plugin-testing-library-6.1.0
branch
# for free
to join this conversation on GitHub.
Already have an account?
# 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-testing-library (5.11.1 → 6.1.0) · Repo
Release Notes
6.1.0
6.0.2
6.0.1
6.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
feat(prefer-implicit-assert): adding new rule (#815)Revert "build(deps-dev): bump prettier from 2.8.7 to 3.0.3 (#825)" (#826)build(deps-dev): bump prettier from 2.8.7 to 3.0.3 (#825)build(deps-dev): bump @babel/eslint-parser from 7.22.9 to 7.22.15 (#822)build(deps-dev): bump eslint-plugin-import from 2.28.0 to 2.28.1 (#821)docs: add justintoman as a contributor for code, and test (#819)fix(await-async-events): sync userEvent.setup() should not be reported (#817)build(deps): bump actions/checkout from 3 to 4 (#813)build(deps-dev): bump @commitlint/config-conventional from 17.6.5 to 17.7.0 (#808)build(deps-dev): bump eslint-plugin-jest from 27.2.1 to 27.2.3 (#807)build(deps-dev): bump del-cli from 5.0.0 to 5.1.0 (#810)build(deps-dev): bump @babel/core from 7.22.9 to 7.22.11 (#809)build(deps-dev): bump @babel/eslint-plugin from 7.22.5 to 7.22.10 (#811)fix(no-await-sync-events): stop reporting `user-event` by default (#803)ci: main pipeline improvements (#799)chore: force releaseci: use automation token for publishing to NPMMerge branch 'main' into alphachore(semantic-release): change package root (#797)chore(jest): replace `ts-jest` with `@swc/jest` (#798)style: format filesrefactor: adjust changes after mergeMerge remote-tracking branch 'origin/main' into alphadocs: add nathanmmiller as a contributor for code, and test (#795)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