Update dependency pytest-cov to v6
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
pytest-cov (changelog) | dev-dependencies | major |
^4.1.0 -> ^6.0.0
|
Release Notes
pytest-dev/pytest-cov (pytest-cov)
v6.2.1
-
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
-
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
- Fixed breakage that occurs when
--cov-context
and theno_cover
marker are used together.
v6.1.0
- Change terminal output to use full width lines for the coverage header.
Contributed by Tsvika Shapira in
#​678 <https://github.com/pytest-dev/pytest-cov/pull/678>
_. - Removed unnecessary CovFailUnderWarning. Fixes
#​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
- 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
- Removed support for xdist rsync (now deprecated).
Contributed by Matthias Reichenbach in
#​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
#​630 <https://github.com/pytest-dev/pytest-cov/pull/630>
,#​631 <https://github.com/pytest-dev/pytest-cov/pull/631>
,#​632 <https://github.com/pytest-dev/pytest-cov/pull/632>
_ and#​633 <https://github.com/pytest-dev/pytest-cov/pull/633>
_. - Added a
pyproject.toml
example in the docs. Contributed by Dawn James in#​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
#​584 <https://github.com/pytest-dev/pytest-cov/pull/584>
_. - Dropped support for Python 3.7.
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Merge request reports
Activity
Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this MR as-is.
Renovate will retry this branch, including artifacts, only when one of the following happens:- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you check the rebase/retry checkbox if found above, or
- you rename this MR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: poetry.lock
Creating virtualenv documento-printserver--_BYpEOJ-py3.10 in /home/ubuntu/.cache/pypoetry/virtualenvs RuntimeError The lock file is not compatible with the current version of Poetry. Upgrade Poetry to be able to read the lock file or, alternatively, regenerate the lock file with the `poetry lock` command. at /usr/local/poetry/1.1.11/venv/lib/python3.10/site-packages/poetry/packages/locker.py:482 in _get_lock_data 478│ "Upgrade Poetry to ensure the lock file is read properly or, alternatively, " 479│ "regenerate the lock file with the `poetry lock` command." 480│ ) 481│ elif not lock_version_allowed: → 482│ raise RuntimeError( 483│ "The lock file is not compatible with the current version of Poetry.\n" 484│ "Upgrade Poetry to be able to read the lock file or, alternatively, " 485│ "regenerate the lock file with the `poetry lock` command." 486│ )
mentioned in issue #8