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

[smartway-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pytest-cov (changelog)	^6.0.0 -> ^7.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

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",
  ]

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 06:59 AM, only on Monday ( * 0-6 * * 1 ) (UTC), 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 has been generated by Renovate Bot.

[github-actions]

🛡️ The security scan result : Repo and Config