Skip to content

chore(deps): update dependency pytest-cov to v6 #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

anaconda-renovate[bot]
Copy link
Contributor

@anaconda-renovate anaconda-renovate bot commented Oct 30, 2024

This PR contains the following updates:

Package Update Change
pytest-cov (changelog) major ==5.0.0 -> ==6.2.1

Release Notes

pytest-dev/pytest-cov (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:

    • "module-not-measured" in workers
    • "already-imported" in subprocesses

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

  • Fixed breakage that occurs when --cov-context and the no_cover marker are used together.

v6.1.0

Compare Source

  • Change terminal output to use full width lines for the coverage header.
    Contributed by Tsvika Shapira in #&#8203;678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.
  • Removed unnecessary CovFailUnderWarning. Fixes #&#8203;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

Compare Source

  • 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.

Configuration

📅 Schedule: Branch creation - "every weekday" in timezone UTC, 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@anaconda-renovate anaconda-renovate bot force-pushed the renovate/pytest-cov-6.x branch 2 times, most recently from fe75722 to 8cc074c Compare April 6, 2025 01:06
@anaconda-renovate anaconda-renovate bot force-pushed the renovate/pytest-cov-6.x branch 2 times, most recently from 205adae to b71f973 Compare June 13, 2025 06:23
@anaconda-renovate anaconda-renovate bot force-pushed the renovate/pytest-cov-6.x branch from b71f973 to 69932e0 Compare June 19, 2025 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants