Update dependency pytest-cov to v5 #34
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/pytest-cov-5.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:
^2.11.1->^5.0.0Release Notes
pytest-dev/pytest-cov (pytest-cov)
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>_.v4.1.0Compare Source
Contributed by Sorin Sbarnea in
#​558 <https://github.com/pytest-dev/pytest-cov/pull/558>_.when
--cov-report=''is used without--cov-fail-under).Contributed by Jonathan Stewmon in
#​589 <https://github.com/pytest-dev/pytest-cov/pull/589>_.Contributed by Matthew Gamble in
#​582 <https://github.com/pytest-dev/pytest-cov/pull/582>_.Contributed by Mark Mayo in
#​572 <https://github.com/pytest-dev/pytest-cov/pull/572>_.Contributed by a bunch of people in
#​565 <https://github.com/pytest-dev/pytest-cov/pull/565>_.v4.0.0Compare Source
Note that this release drops support for multiprocessing.
--cov-fail-underno longer causespytest --collect-onlyto failContributed by Zac Hatfield-Dodds in
#​511 <https://github.com/pytest-dev/pytest-cov/pull/511>_.Dropped support for multiprocessing (mostly because
issue 82408 <https://github.com/python/cpython/issues/82408>_). This feature wasmostly working but very broken in certain scenarios and made the test suite very flaky and slow.
There is builtin multiprocessing support in coverage and you can migrate to that. All you need is this in your
.coveragerc::Fixed deprecation in
setup.pyby trying to import setuptools before distutils.Contributed by Ben Greiner in
#​545 <https://github.com/pytest-dev/pytest-cov/pull/545>_.Removed undesirable new lines that were displayed while reporting was disabled.
Contributed by Delgan in
#​540 <https://github.com/pytest-dev/pytest-cov/pull/540>_.Documentation fixes.
Contributed by Andre Brisco in
#​543 <https://github.com/pytest-dev/pytest-cov/pull/543>_and Colin O'Dell in
#​525 <https://github.com/pytest-dev/pytest-cov/pull/525>_.Added support for LCOV output format via
--cov-report=lcov. Only works with coverage 6.3+.Contributed by Christian Fetzer in
#​536 <https://github.com/pytest-dev/pytest-cov/pull/536>_.Modernized pytest hook implementation.
Contributed by Bruno Oliveira in
#​549 <https://github.com/pytest-dev/pytest-cov/pull/549>_and Ronny Pfannschmidt in
#​550 <https://github.com/pytest-dev/pytest-cov/pull/550>_.v3.0.0Compare Source
Note that this release drops support for Python 2.7 and Python 3.5.
Contributed by Hugo van Kemenade in
#​500 <https://github.com/pytest-dev/pytest-cov/pull/500>_.#​494 <https://github.com/pytest-dev/pytest-cov/pull/494>_ and#​495 <https://github.com/pytest-dev/pytest-cov/pull/495>_.--cov-resetCLI option.Contributed by Danilo Šegan in
#​459 <https://github.com/pytest-dev/pytest-cov/pull/459>_.--cov-fail-underCLI option.Contributed by ... Ronny Pfannschmidt's desire for skark in
#​480 <https://github.com/pytest-dev/pytest-cov/pull/480>_.Contributed by Thomas Grainger in
#​488 <https://github.com/pytest-dev/pytest-cov/pull/488>_.#​481 <https://github.com/pytest-dev/pytest-cov/pull/481>_.tomlrequirement.Contributed by Thomas Grainger in
#​477 <https://github.com/pytest-dev/pytest-cov/pull/477>_.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 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.