chore(deps): update dependency pytest-cov to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-cov (changelog)	^4.1.0 -> ^7.0.0

---

Release Notes

pytest-dev/pytest-cov (pytest-cov)

v7.0.0

Compare Source

• Dropped support for subprocesses measurement.

  It was a feature added long time ago when coverage lacked a nice way to measure subprocesses created in tests.
  It relied on a .pth file, there was no way to opt-out and it created bad interations
  with coverage's new patch system <https://coverage.readthedocs.io/en/latest/config.html#run-patch>_ added
  in 7.10 <https://coverage.readthedocs.io/en/7.10.6/changes.html#version-7-10-0-2025-07-24>_.

  To migrate to this release you might need to enable the suprocess patch, example for .coveragerc:

  .. code-block:: ini

  [run]
  patch = subprocess

  This release also requires at least coverage 7.10.6.

• Switched packaging to have metadata completely in pyproject.toml and use hatchling <https://pypi.org/project/hatchling/>_ for
  building.
  Contributed by Ofek Lev in #&#8203;551 <https://github.com/pytest-dev/pytest-cov/pull/551>_
  with some extras in #&#8203;716 <https://github.com/pytest-dev/pytest-cov/pull/716>_.

• Removed some not really necessary testing deps like six.

v6.3.0

Compare Source

• Added support for markdown reports.
  Contributed by Marcos Boger in #&#8203;712 <https://github.com/pytest-dev/pytest-cov/pull/712>_
  and #&#8203;714 <https://github.com/pytest-dev/pytest-cov/pull/714>_.
• Fixed some formatting issues in docs.
  Anonymous contribution in #&#8203;706 <https://github.com/pytest-dev/pytest-cov/pull/706>_.

v6.2.1

Compare Source

• Added a version requirement for pytest's pluggy dependency (1.2.0, released 2023-06-21) that has the required new-style hookwrapper API.

• Removed deprecated license classifier (packaging).

• Disabled coverage warnings in two more situations where they have no value:

  • "module-not-measured" in workers
  • "already-imported" in subprocesses

v6.2.0

Compare Source

• The plugin now adds 3 rules in the filter warnings configuration to prevent common coverage warnings being raised as obscure errors::

  default:unclosed database in <sqlite3.Connection object at:ResourceWarning
  once::PytestCovWarning
  once::CoverageWarning

  This fixes most of the bad interactions that are occurring on pytest 8.4 with filterwarnings=error.

  The plugin will check if there already matching rules for the 3 categories
  (ResourceWarning, PytestCovWarning, CoverageWarning) and message (unclosed database in <sqlite3.Connection object at) before adding the filters.

  This means you can have this in your pytest configuration for complete oblivion (not recommended, if that is not clear)::

  filterwarnings = [
  "error",
  "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning",
  "ignore::PytestCovWarning",
  "ignore::CoverageWarning",
  ]

v6.1.1

Compare Source

• Fixed breakage that occurs when --cov-context and the no_cover marker are used together.

v6.1.0

Compare Source

• Change terminal output to use full width lines for the coverage header.
  Contributed by Tsvika Shapira in #&#8203;678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.
• Removed unnecessary CovFailUnderWarning. Fixes #&#8203;675 <https://github.com/pytest-dev/pytest-cov/issues/675>_.
• Fixed the term report not using the precision specified via --cov-precision.

v6.0.0

Compare Source

• Updated various documentation inaccuracies, especially on subprocess handling.
• Changed fail under checks to use the precision set in the coverage configuration.
  Now it will perform the check just like coverage report would.
• Added a --cov-precision cli option that can override the value set in your coverage configuration.
• Dropped support for now EOL Python 3.8.

v5.0.0

Compare Source

• Removed support for xdist rsync (now deprecated).
  Contributed by Matthias Reichenbach in #&#8203;623 <https://github.com/pytest-dev/pytest-cov/pull/623>_.
• Switched docs theme to Furo.
• Various legacy Python cleanup and CI improvements.
  Contributed by Christian Clauss and Hugo van Kemenade in
  #&#8203;630 <https://github.com/pytest-dev/pytest-cov/pull/630>,
  #&#8203;631 <https://github.com/pytest-dev/pytest-cov/pull/631>,
  #&#8203;632 <https://github.com/pytest-dev/pytest-cov/pull/632>_ and
  #&#8203;633 <https://github.com/pytest-dev/pytest-cov/pull/633>_.
• Added a pyproject.toml example in the docs.
  Contributed by Dawn James in #&#8203;626 <https://github.com/pytest-dev/pytest-cov/pull/626>_.
• Modernized project's pre-commit hooks to use ruff. Initial POC contributed by
  Christian Clauss in #&#8203;584 <https://github.com/pytest-dev/pytest-cov/pull/584>_.
• Dropped support for Python 3.7.

---

Configuration

📅 Schedule: 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[BrandtKruger]

Create new PR with changes as I can not add changes in PR

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x releases. But if you manually upgrade to 7.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.