chore(deps): update dependency coverage to v7.15.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
coverage	==7.15.1 → ==7.15.2

---

Release Notes

coveragepy/coveragepy (coverage)

v7.15.2

Compare Source

• Fix: one of the performance improvements in 7.15.1 (pull 2215) dramatically
  increased memory use during reporting for large projects. Now we use a
  different approach that is both faster and slimmer than 7.15.0. Fixes issue 2229_.

.. _issue 2229: #​2229

.. _changes_7-15-1:

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

LGTM — trivial dev-dependency patch bump (coverage 7.15.1 → 7.15.2), a memory-usage fix in coverage's reporting code with no functional impact on this repo.

What was reviewed: confirmed the diff is limited to a single pinned version line in requirements-dev.txt (a dev-only, pip-compile-generated lockfile), matching the Renovate PR description; no other lines or dependencies changed.

Extended reasoning...

Overview

Single-line change in requirements-dev.txt bumping the pinned version of coverage (a dev/test dependency used via pytest-cov) from 7.15.1 to 7.15.2. This is an auto-generated lockfile maintained by pip-compile, not hand-written code, and coverage is not a runtime dependency of pyUSPTO itself.

Security risks

None. coverage is a test-tooling package, not part of the shipped library or its runtime dependency graph. The upstream release note describes a memory-usage regression fix in coverage's own reporting code, unrelated to security.

Level of scrutiny

Minimal scrutiny is appropriate: this is a mechanical Renovate-generated dependency bump to a dev-only tool, with no code changes in the repository itself and no behavioral surface to test.

Other factors

No prior reviews or comments on this PR. The change is self-contained, matches the PR description exactly, and pip-compile lockfiles are low-risk to auto-approve.