hads/hinpdof
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(deps): update dependency pytest-cov to v6.2.1 #60

Merged
hads merged 1 commits from renovate/pytest-cov-6.x-lockfile into main 2025-06-19 09:52:01 +12:00
Conversation 0 Commits 1 Files Changed 1 +5 -4
hads commented 2025-06-12 12:03:47 +12:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
pytest-cov (changelog) dev minor 6.1.1 -> 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",
    ]

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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [pytest-cov](https://github.com/pytest-dev/pytest-cov) ([changelog](https://pytest-cov.readthedocs.io/en/latest/changelog.html)) | dev | minor | `6.1.1` -> `6.2.1` | --- ### Release Notes <details> <summary>pytest-dev/pytest-cov (pytest-cov)</summary> ### [`v6.2.1`](https://github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#621-2025-06-12) [Compare Source](https://github.com/pytest-dev/pytest-cov/compare/v6.2.0...v6.2.1) - 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`](https://github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#620-2025-06-11) [Compare Source](https://github.com/pytest-dev/pytest-cov/compare/v6.1.1...v6.2.0) - 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", ] </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC40OS4xMiIsInVwZGF0ZWRJblZlciI6IjQwLjUwLjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
hads added 1 commit 2025-06-12 12:03:47 +12:00
chore(deps): update dependency pytest-cov to v6.2.0
All checks were successful
Build and Publish Docker Image / build (pull_request) Successful in 1m23s
Details
6c8a7e93b2
hads force-pushed renovate/pytest-cov-6.x-lockfile from 6c8a7e93b2 to 5e46fe67af 2025-06-13 00:04:19 +12:00 Compare
hads changed title from chore(deps): update dependency pytest-cov to v6.2.0 to chore(deps): update dependency pytest-cov to v6.2.1 2025-06-13 00:04:20 +12:00
hads merged commit 2bab55a0ff into main 2025-06-19 09:52:01 +12:00
hads deleted branch renovate/pytest-cov-6.x-lockfile 2025-06-19 09:52:02 +12:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hads
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hads/hinpdof#60
No description provided.
Delete Branch "renovate/pytest-cov-6.x-lockfile"

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?