Update @testing-library/jest-dom 5.12.0 → 5.17.0 (minor) #122
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @testing-library/jest-dom (5.12.0 → 5.17.0) · Repo · Changelog
Release Notes
5.17.0
5.16.5
5.16.4
5.16.3
5.16.2
5.16.1
5.16.0
5.15.1
5.15.0
5.14.1
5.14.0
5.13.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 31 commits:
feat: New `toHaveAccessibleErrorMessage` better implementing the spec, deprecate `toHaveErrorMessage` (#503)fix: migrate ccs v3 to @adobe/css-tools v4 (#470)fix: Support unenclosed inner text for details elements in to be visible (#396)fix: clarify toHaveFocus message when using `.not` (#447)docs: add ashleyryan as a contributor for code, ideas (#434)docs: add astorije as a contributor for code, ideas (#433)fix: add custom element support to `toBeDisabled` (#368)docs: add cbroeren as a contributor for doc (#432)docs: Fix wrong toHaveValue example (#431)fix: Improve `toHaveClass` error message format (#405)docs: add IanVS as a contributor for code (#423)feat: Update aria-query to 5.0.0 (#414)fix: wrong deprecate error message (#422)feat: import parse directly from css (#415)docs: add yannbf as a contributor for code (#416)docs: add MatanBobi as a contributor for platform (#410)chore: set protocol for npm to `https` (#409)docs: add tu4mo as a contributor for doc (#386)chore: upgrade to Jest 27 (#384)Fix typo (#385)docs: add icecream17 as a contributor for doc (#381)fix grammar (#380)fix: Updates deprecated matchers info (#378)feat: toHaveAccessibleName and toHaveAccessibleDescription (#377)docs: Update the documentation of toBeDisabled (#375)docs: add julienw as a contributor (#374)docs: Fix typo in README (#373)docs: add SevenOutman as a contributor (#372)feat: Add `toHaveErrorMessage` matcher (#370)doc: Better documentation for toContaintHTML (#363)chore: continue testing on Node 15 (#360)👉 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:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `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