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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
coverage	==7.16.0 → ==7.16.1

---

Release Notes

coveragepy/coveragepy (coverage)

v7.16.1

Compare Source

• Fix: when the body of an irrefutable case (like case _:) is entirely
  excluded, the case line is now excluded too, just as an excluded
  else: body removes the else: line. Previously the case line was
  left behind and reported as missing. Closes issue 1563_ with pull 2269_.

• Fix: using :meth:.CoverageData.update twice on an in-memory database would
  fail, as described in issue 2279_. This is now fixed.

.. _issue 1563: #​1563
.. _pull 2269: #​2269
.. _issue 2279: #​2279

.. _changes_7-16-0:

---

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, straightforward dependency version bump. Checked the diff: it only bumps the pinned coverage package from 7.16.0 to 7.16.1 in requirements-dev.txt, a patch release with only bug fixes per the changelog (excluded case line handling and an in-memory CoverageData.update fix), no other files or lines touched.

Extended reasoning...

Overview

The entire change is a single line in requirements-dev.txt, bumping the pinned dev-only dependency coverage (used transitively via pytest-cov) from 7.16.0 to 7.16.1. Verified via git diff that no other files or lines are affected.

Security risks

None. This is a test/dev tooling dependency, not part of the shipped application, and the version bump is a patch release from the official coveragepy project containing only bug fixes (excluded case statement handling, in-memory database update fix). No new attack surface, no code execution paths changed.

Level of scrutiny

Minimal scrutiny is appropriate: this is a mechanical, automated Renovate dependency bump on a dev-only tool with a single-character version change, no ambiguity, and a well-documented, low-risk changelog.

Other factors

No CODEOWNERS restrictions apply, no prior review comments to address, and the bug-hunting system found no issues. This is exactly the kind of trivial, self-contained change safe to approve without further human review.