Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 11, 2025

This PR contains the following updates:

Package Change Age Confidence
pytest-cov (changelog) ==6.1.1 -> ==6.3.0 age confidence

Release Notes

pytest-dev/pytest-cov (pytest-cov)

v6.3.0

Compare Source

  • Added support for markdown reports.
    Contributed by Marcos Boger in #&#8203;712 <https://github.com/pytest-dev/pytest-cov/pull/712>_
    and #&#8203;714 <https://github.com/pytest-dev/pytest-cov/pull/714>_.
  • Fixed some formatting issues in docs.
    Anonymous contribution in #&#8203;706 <https://github.com/pytest-dev/pytest-cov/pull/706>_.

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",
    ]


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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added kind/dependencies Pull requests that update a dependency file skip/changelog If it should be excluded from changelog or Release notes. Such as infra, reverted PRs, etc. tests/skip This PR does not require integration tests to be run. labels Jun 11, 2025
@sourcery-ai
Copy link

sourcery-ai bot commented Jun 11, 2025

Reviewer's Guide

Upgrade pytest-cov to v6.2.0 by updating the version declaration in the project’s requirements file.

Sequence Diagram: pytest-cov v6.2.0 Setup of Default Warning Filters

sequenceDiagram
    participant P as Pytest
    participant PCov_New as "pytest-cov v6.2.0"
    participant PWF as "Pytest Warning Filter System"

    P->>PCov_New: Load Plugin
    PCov_New->>PWF: Add Default Warning Filter Rules (New Behavior in v6.2.0)
Loading

File-Level Changes

Change Details Files
Bump pytest-cov dependency version
  • Change version from 6.1.1 to 6.2.0 in requirements
.devcontainer/alma9/requirements.txt

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@has-bot
Copy link
Member

has-bot commented Jun 11, 2025

This PR does not require integration tests to be run.


Comment generated by an automation.

@has-bot
Copy link
Member

has-bot commented Jun 11, 2025

This PR does not require integration tests to be run.


Comment generated by an automation.

@codecov
Copy link

codecov bot commented Jun 11, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.11%. Comparing base (254edf1) to head (7b69140).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1473   +/-   ##
=======================================
  Coverage   96.11%   96.11%           
=======================================
  Files          72       72           
  Lines        5176     5176           
  Branches      895      895           
=======================================
  Hits         4975     4975           
  Misses        119      119           
  Partials       82       82           
Flag Coverage Δ
centos-linux-7 91.63% <ø> (ø)
centos-linux-8 92.49% <ø> (ø)
centos-linux-9 92.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate renovate bot changed the title chore(deps): update dependency pytest-cov to v6.2.0 chore(deps): update dependency pytest-cov to v6.2.1 Jun 12, 2025
@renovate renovate bot force-pushed the renovate/pytest-cov-6.x branch from 50883bb to 119b3d5 Compare June 12, 2025 14:14
@renovate renovate bot changed the title chore(deps): update dependency pytest-cov to v6.2.1 chore(deps): update dependency pytest-cov to v6.3.0 Sep 6, 2025
@renovate renovate bot force-pushed the renovate/pytest-cov-6.x branch from 119b3d5 to 7b69140 Compare September 6, 2025 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/dependencies Pull requests that update a dependency file skip/changelog If it should be excluded from changelog or Release notes. Such as infra, reverted PRs, etc. tests/skip This PR does not require integration tests to be run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants