profitroll/LibBotUniversal
1
0
Fork 0
Code Issues 4 Pull Requests 1 Actions Packages Releases 39 Wiki Activity

Update dependency pytest-cov to v6.2.0 #214

Merged
Renovate merged 1 commits from renovate/pytest-cov-6.x into dev 2025-06-12 01:55:02 +03:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
Renovate commented 2025-06-12 01:32:33 +03:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
pytest-cov (changelog) minor ==6.1.1 -> ==6.2.0

Release Notes

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

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: Enabled.

♻ 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 | Update | Change | |---|---|---| | [pytest-cov](https://github.com/pytest-dev/pytest-cov) ([changelog](https://pytest-cov.readthedocs.io/en/latest/changelog.html)) | minor | `==6.1.1` -> `==6.2.0` | --- ### Release Notes <details> <summary>pytest-dev/pytest-cov (pytest-cov)</summary> ### [`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**: Enabled. ♻ **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:eyJjcmVhdGVkSW5WZXIiOiIzNi4zNS4wIiwidXBkYXRlZEluVmVyIjoiMzYuMzUuMCIsInRhcmdldEJyYW5jaCI6ImRldiJ9-->
Renovate added 1 commit 2025-06-12 01:32:34 +03:00
Update dependency pytest-cov to v6.2.0
All checks were successful
Analysis / SonarCloud (pull_request) Successful in 50s
Details
Tests / Build and Test (3.11) (pull_request) Successful in 1m24s
Details
Tests / Build and Test (3.12) (pull_request) Successful in 1m34s
Details
Tests / Build and Test (3.13) (pull_request) Successful in 1m11s
Details
Analysis / SonarCloud (push) Successful in 49s
Details
38bf43a5e7
Renovate scheduled this pull request to auto merge when all checks succeed 2025-06-12 01:32:34 +03:00
Renovate merged commit 38bf43a5e7 into dev 2025-06-12 01:55:02 +03:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
Renovate profitroll
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: profitroll/LibBotUniversal#214
No description provided.
Delete Branch "renovate/pytest-cov-6.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?