Update dependency pytest-cov to v7 #390
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot]
.This notice will be removed on 2025-10-07.
This PR contains the following updates:
~=5.0.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 interationswith
coverage's new patch system <https://coverage.readthedocs.io/en/latest/config.html#run-patch>
_ addedin
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 usehatchling <https://pypi.org/project/hatchling/>
_ forbuilding.
Contributed by Ofek Lev in
#​551 <https://github.com/pytest-dev/pytest-cov/pull/551>
_with some extras in
#​716 <https://github.com/pytest-dev/pytest-cov/pull/716>
_.Removed some not really necessary testing deps like
six
.v6.3.0
Compare Source
Contributed by Marcos Boger in
#​712 <https://github.com/pytest-dev/pytest-cov/pull/712>
_and
#​714 <https://github.com/pytest-dev/pytest-cov/pull/714>
_.Anonymous contribution in
#​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:
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
--cov-context
and theno_cover
marker are used together.v6.1.0
Compare Source
Contributed by Tsvika Shapira in
#​678 <https://github.com/pytest-dev/pytest-cov/pull/678>
_.#​675 <https://github.com/pytest-dev/pytest-cov/issues/675>
_.--cov-precision
.v6.0.0
Compare Source
Now it will perform the check just like
coverage report
would.--cov-precision
cli option that can override the value set in your coverage configuration.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.
This PR was generated by Mend Renovate. View the repository job log.