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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
depfu[bot]
commented
4 months ago
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.4.6) · 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 51 commits:
fix: Support @starting-style (#602)fix: add js suffix to isEqualWith import (#599)fix(infra): codecoverage token addition (#600)fix: Updates role support for aria-required attribute in `toBeRequired` (#590)refactor: replace lodash with own implementation when possible (#593)fix: Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#575)docs: add Dennis273 as a contributor for code (#581)docs: add kryops as a contributor for bug, code, and test (#580)docs: add SteKoe as a contributor for bug, and code (#579)docs: add jakeboone02 as a contributor for code, and test (#578)docs: add fpapado as a contributor for code, doc, and test (#573)fix: Export type `TestingLibraryMatchers` from "./matchers" (#576)feat: Add toHaveRole matcher (#572)feat: Support for regular expressions in toHaveClass (#563)fix: Standalone types for "./matchers" export and add Bun support (#566)feat: toHaveAccessibleDescription supports aria-description (#565)fix: Upgrade @adobe/css-tools to v4.3.2 (#553)docs: Fix typo at toHaveStyle function description (#558)fix: support uppercase custom props in toHaveStyle (#552)docs: Add missing hr to README.md (#550)fix: upgrade `@adobe/css-tools` to `4.3.1` to address vulnerability (#532)chore: add jest/vitest version to bug report template (#526)fix: proper @jest/globals import (#530)fix: bump @adobe/css-tools for ESM support (#525)fix(package.json): update main and module file paths (#523)feat: manually trigger release (#520)chore: Publish ESM and CJS (#519)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)🆕 @adobe/css-tools (added, 4.4.0)
🆕 dequal (added, 2.0.3)
🗑️ @types/jest (removed)
🗑️ @types/testing-library__jest-dom (removed)
👉 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