Closed depfu[bot] closed 1 year ago
Closed in favor of #244.
Closed in favor of #249.
Closed in favor of #260.
Closed in favor of #273.
Closed in favor of #278.
Closed in favor of #280.
Closed in favor of #288.
Closed in favor of #289.
Closed in favor of #293.
Closed in favor of #294.
Closed in favor of #295.
Closed in favor of #316.
Closed in favor of #330.
Closed in favor of #337.
Closed in favor of #345.
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?
✳️ @testing-library/jest-dom (5.14.1 → 6.0.1) · Repo · Changelog
Release Notes
6.0.1
6.0.0
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
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
fix: matchers type is making the global expect unsafe (#513)
feat: local types, supporting jest, @jest/globals, vitest (#511)
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)
👉 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