chore(deps-dev): bump @testing-library/jest-dom from 6.10.0 to 7.0.0

[dependabot]

Bumps @testing-library/jest-dom from 6.10.0 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

Commits

• 1e39089 feat: add toContainAnyBy* and toContainOneBy* query matchers
• 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)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0977bf79be

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Commit the lockfile update with the dependency bump

This changes package.json to require @testing-library/jest-dom ^7.0.0, but the committed bun.lock still records the root devDependency as ^6.9.1 and resolves @testing-library/jest-dom@6.9.1. I checked the root CI install step at .github/workflows/ci.yml:37, which runs bun install --frozen-lockfile; Bun's help says that flag disallows lockfile changes, so fresh CI/Docker installs from this commit will not be able to reconcile the manifest and lockfile until the lockfile is regenerated and committed.

Useful? React with 👍 / 👎.

[krishagel]

🤖 pr-fix routine: blocked — cannot regenerate bun.lock in this environment

Diagnosis (confirmed from logs, not inferred):

Four checks fail — Test, Lint, and Type Check, Auth Edge Production Artifact, Validate CDK Infrastructure, and Unified Content PostgreSQL Lifecycle — and all four die at the same step, before any test runs:

error: lockfile had changes, but lockfile is frozen
note: try re-running without --frozen-lockfile and commit the updated lockfile

This PR bumps package.json to "@testing-library/jest-dom": "^7.0.0" but leaves bun.lock pinning the old resolution:

bun.lock:174:   "@testing-library/jest-dom": "^6.9.1",
bun.lock:1324:  "@testing-library/jest-dom": ["@testing-library/jest-dom@6.9.1", ...]

bun install --frozen-lockfile is correctly refusing. dev is green, so this is PR-caused, not a pre-existing base failure.

Why I could not fix it: the fix is bun install + commit the lockfile. registry.npmjs.org is not in this session's network egress allowlist — it returns 403 both directly and through the agent proxy (Host not in allowlist: registry.npmjs.org). Writing a lockfile entry requires the package's real sha512 integrity hash from the registry, and I will not fabricate one.

This is systemic, not specific to this PR. I verified the file lists of the other open Dependabot PRs — every one touches package.json (or infra/package.json) and never the matching lockfile:

PR	Files changed
#1567	infra/package.json only
#1568	package.json only
#1569	package.json only
#1570	package.json only
#1571 (this)	package.json only

Same cause as the one already written up on #1566: .github/dependabot.yml declares package-ecosystem: "npm", but this repo has no package-lock.json/yarn.lock — it uses bun.lock. Dependabot's npm ecosystem edits manifests only and cannot maintain bun.lock, so every Dependabot PR desyncs the lockfile and fails --frozen-lockfile. That accounts for the whole pr-fix-stuck pile (#1563, #1566, #1572–#1576) plus #1567–#1571.

Two ways out, both requiring a human:

1. Per-PR: run bun install on each branch and push the updated lockfile.
2. Once, permanently: switch .github/dependabot.yml to package-ecosystem: "bun" for / and /infra so Dependabot maintains bun.lock itself. I deliberately did not make this change — it reshapes every future dependency PR and I can't validate it from here, so it should be your call.

Unblocking the routine itself would additionally require adding registry.npmjs.org to the cloud environment's egress allowlist; without it this routine cannot fix any lockfile-desync PR.

The routine will not pick this PR up again until someone removes the pr-fix-stuck label.

---

Generated by Claude Code