Update dependency pytest-cov to v6 - autoclosed #77
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
3 times, most recently
from
ddcf5f7 to
3051230
Compare
|
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
from
3051230 to
e05d7e0
Compare
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
from
e05d7e0 to
12c5573
Compare
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
2 times, most recently
from
d21e8b5 to
a599725
Compare
|
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
from
a599725 to
90c50a5
Compare
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
2 times, most recently
from
45fa8ed to
6c9596e
Compare
|
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
from
6c9596e to
b3ae9cb
Compare
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
from
b3ae9cb to
7fd9e59
Compare
renovate
bot
force-pushed
the
renovate/pytest-cov-6.x-lockfile
branch
from
7fd9e59 to
26db884
Compare
|
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
4.1.0->6.3.0Release Notes
pytest-dev/pytest-cov (pytest-cov)
v6.3.0Compare 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.1Compare 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.0Compare 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.1Compare Source
--cov-contextand theno_covermarker are used together.v6.1.0Compare 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.0Compare Source
Now it will perform the check just like
coverage reportwould.--cov-precisioncli option that can override the value set in your coverage configuration.v5.0.0Compare 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.tomlexample 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: Branch creation - "after 7am on Friday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.