chore(deps): update dependency pytest-cov to v6 #35
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/pytest-cov-6.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^4.1.0
->^6.0.0
Release Notes
pytest-dev/pytest-cov
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.v5.0.0
Compare Source
Contributed by Matthias Reichenbach in
#​623 <https://github.com/pytest-dev/pytest-cov/pull/623>
_.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>
_.pyproject.toml
example in the docs.Contributed by Dawn James in
#​626 <https://github.com/pytest-dev/pytest-cov/pull/626>
_.Christian Clauss in
#​584 <https://github.com/pytest-dev/pytest-cov/pull/584>
_.Configuration
📅 Schedule: 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 has been generated by Renovate Bot.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: poetry.lock
Checkout
From your project repository, check out a new branch and test the changes.