Bump @testing-library/jest-dom from 5.17.0 to 6.1.4

[dependabot]

Bumps @testing-library/jest-dom from 5.17.0 to 6.1.4.

Release notes

Sourced from @​testing-library/jest-dom's releases.

v6.1.4

6.1.4 (2023-10-12)

Bug Fixes

• upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#532) (44f1eab)

v6.1.3

6.1.3 (2023-09-06)

Bug Fixes

• proper @​jest/globals import (#530) (5b492ac)

v6.1.2

6.1.2 (2023-08-24)

Bug Fixes

• bump @​adobe/css-tools for ESM support (#525) (b959a68)

v6.1.1

6.1.1 (2023-08-23)

Bug Fixes

• package.json: update main and module file paths (#523) (853a3e5)

v6.1.0

6.1.0 (2023-08-23)

Features

• Publish ESM and CJS (testing-library/jest-dom#519)

v6.0.1

6.0.1 (2023-08-18)

Bug Fixes

• matchers type is making the global expect unsafe (#513) (bdb34f1)

... (truncated)

Commits

• 44f1eab fix: upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#532)
• 6d65999 chore: add jest/vitest version to bug report template (#526)
• 5b492ac fix: proper @​jest/globals import (#530)
• b959a68 fix: bump @​adobe/css-tools for ESM support (#525)
• 853a3e5 fix(package.json): update main and module file paths (#523)
• 3d834bb feat: manually trigger release (#520)
• 61d17bd chore: Publish ESM and CJS (#519)
• bdb34f1 fix: matchers type is making the global expect unsafe (#513)
• 4b764b9 feat: local types, supporting jest, @​jest/globals, vitest (#511)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of our deployment process below:

1. 👀 Observe the CI jobs and tests to ensure they are passing

2. ✔️ Obtain an approval/review on this pull request

3. 🚀 Deploy your pull request to the development environment with .deploy to development

4. 🚀 Deploy your pull request to the production environment with .deploy

   If anything goes wrong, rollback with .deploy main

5. 🎉 Merge!

Note: If you have a larger change and want to block deployments, you can run .lock --reason <reason> to lock all other deployments (remove with .unlock)

You can view the branch deploy usage guide for additional information

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.