Bump @testing-library/jest-dom from 6.9.1 to 7.0.0

[dependabot]

Bumps @testing-library/jest-dom from 6.9.1 to 7.0.0.

Release notes

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

v7.0.0

7.0.0 (2026-07-20)

Features

• add toContainAnyBy* and toContainOneBy* query matchers (1e39089)

BREAKING CHANGES

• @​testing-library/dom is now a required peer dependency. The minimum supported Node.js version is now 22.

Repaired release for testing-library/jest-dom#731

v6.10.0

6.10.0 (2026-07-20)

Features

• add toContainAnyBy* and toContainOneBy* query matchers (#731) (cae44df)

Commits

• 1e39089 feat: add toContainAnyBy* and toContainOneBy* query matchers
• cae44df feat: add toContainAnyBy* and toContainOneBy* query matchers (#731)
• 55c07ce ci: switch release to npm trusted publishing (#726)
• 213256f docs: move toHaveSelection from the deprecated section (#717)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​testing-library/jest-dom since your current version.

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 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)

[diffy-bot]

Summary

• Bumped @testing-library/jest-dom in apps/web/package.json from ^6.8.0 to ^7.0.0.
• Updated pnpm-lock.yaml to reflect that upgrade and a set of transitive dependency version bumps (lockfile snapshots and package entries updated).

Files changed

• apps/web/package.json
  • devDependencies: "@testing-library/jest-dom" ^6.8.0 → ^7.0.0
• pnpm-lock.yaml
  • Updated lock entries/snapshots for @testing-library/jest-dom and several transitive deps.

Notable/details

• @testing-library/jest-dom

  • specifier: ^6.8.0 → ^7.0.0
  • version in lockfile: 6.9.1 → 7.0.0(@testing-library/dom@10.4.1)
  • lockfile package entry changed to '@testing-library/jest-dom@7.0.0' with:
    • new resolution integrity
    • engines: node: '>=22' (previously node: '>=14')
    • peerDependencies: '@testing-library/dom': '>=10 <11'
  • snapshot entries adjusted to reflect new package and dependency on @testing-library/dom@10.4.1

• Transitive package/version bumps in pnpm-lock.yaml (examples)

  • baseline-browser-mapping: 2.10.40 → 2.11.1
  • browserslist: 4.28.4 → 4.28.7
  • caniuse-lite: 1.0.30001799 → 1.0.30001806
  • electron-to-chromium: 1.5.380 → 1.5.396
  • node-releases: 2.0.50 → 2.0.51
  • update-browserslist-db snapshot now points to browserslist@4.28.7

• Multiple snapshot sections and package resolution integrities were updated to match the new versions.

Suggestions

• Node engine compatibility: @testing-library/jest-dom@7 declares engines.node >=22. Confirm your CI and development environments (and any package manager engines checks) support Node 22+. If your project runs on Node 18 or 20, this could cause install failures or warnings. Consider:
  • Downgrading to a 6.x release of jest-dom if you must stay on Node 18/20, or
  • Upgrading Node in CI/environments to >=22.
• Peer dependency: jest-dom@7 requires '@testing-library/dom' >=10 <11. Ensure @testing-library/dom is present (added automatically in the lockfile snapshot here) or add it explicitly to devDependencies to avoid peerDep warnings.
• Run full test suite and linters after this upgrade to catch any breaking API changes between jest-dom v6 → v7.
• If you don't intend to change Node engine requirements, prefer pinning to a version of jest-dom compatible with your current Node version.

You can generate a new summary by commenting @diffy-bot.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​testing-library/​jest-dom@​7.0.0

View full report