build(deps-dev): bump @testing-library/jest-dom from 6.9.1 to 7.0.1

[dependabot]

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

Release notes

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

v7.0.1

7.0.1 (2026-08-09)

Bug Fixes

• declare vitest as an optional peer dependency (#733) (3782c78)

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

• 3782c78 fix: declare vitest as an optional peer dependency (#733)
• 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)

---

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a.

• Head SHA: 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a

• Workflow run: 32172983862

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a
• Workflow run: 32180576805
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a.

• Head SHA: 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a

• Workflow run: 32180576805

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]

Loading

[opencode-agent]

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

• Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

• Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

• Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

• Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

• Result: REQUEST_CHANGES

• Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a.

• Head SHA: 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a

• Workflow run: 32180576805

• Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (2 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (2 files)"]
  R1 --> V1["required checks"]

Loading

[seonghobae]

Reviewed exact head 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a against protected develop@acdbea6344fe1231c39535b575f4de35e4c607c9. The change is limited to @testing-library/jest-dom 7.0.1 plus lockfile resolution; BandScope's declared Node 22 range satisfies jest-dom's Node >=22 floor, the required @testing-library/dom peer resolves at 10.4.1, and exact-head ci, build-baseline, release, sbom, Bandit, SAST Semgrep, and secret-scan are terminal-success. The PR-introduced OSV comparison and dependency-review jobs are also success. The aggregate security failure was inspected at job/log level and is the protected-base pdfjs-dist CVE-2026-16633 owned by canonical #783, not introduced by this dependency bump. No inline review threads are open. APPROVE is code-review evidence only; it does not treat the inherited #783 security failure or the central coverage/OpenCode prerequisite as passing and does not authorize merge until those exact-head gates are regenerated and green.

[seonghobae]

Current-head re-review found a branch-owned lock-provenance regression that my earlier approval missed. The exact package-lock.json diff removes peer: true from the root node_modules/@esbuild/* platform records. Canonical dependency-security owner #783 makes preservation of those npm-10.9.8-generated markers an explicit regression sentinel for future dependency updates. Please regenerate/recreate this jest-dom update from the protected develop produced after #783 merges, using npm 10.9.8, and then require frozen npm ci plus the full exact-head test/security cycle. Do not hand-edit generator-sensitive lock metadata. This REQUEST_CHANGES supersedes my earlier approval; the jest-dom 7.0.1 dependency intent and its Node/peer requirements are not the objection.

[devin-ai-integration]

Devin Review found 2 potential issues.

🐛 1 issue in files not directly in the diff

🐛 Merge conflict markers left in lockfile

The committed package-lock.json still contains Git conflict markers <<<<<<< HEAD (line 64), ======= (line 343), and >>>>>>> origin/develop (line 344). The file is no longer valid JSON, so npm install and every lockfile-dependent CI gate fail.

[seonghobae]

@opencode-agent Review PR #929 only at exact current head aac5e3becb3349c8e320c5bccd459567a6d30665 against protected develop@749511c3ad4000090048718f685c6bee6b3d2c25. Refetch the exact head/base, diff/tree, current threads, reviews, and exact-head checks first; predecessor OpenCode verdicts on 0ce4cb84cbafcc81cbd824b2a7879ab5549d419a are stale. Verify the jest-dom 7 breaking-boundary explicitly: repository Node is >=22.13 <23, the current lock installs @testing-library/dom 10.4.1 satisfying jest-dom 7.0.1's required >=10 <11 peer, @testing-library/react 16.3.2 remains present, and the lock now resolves the desktop jest-dom installation to 7.0.1. The current required OpenCode workflow's bootstrap, coverage-source-tree, and coverage-evidence jobs succeeded; final job 98807628166 in run 33158529352 failed closed only because no current-head verdict existed. Submit a formal current-head APPROVED or CHANGES_REQUESTED verdict. Do not modify source, self-approve, weaken gates, or transfer predecessor evidence.