Skip to content

[pull] master from aio-libs:master#274

Merged
pull[bot] merged 1 commit intotj-python:masterfrom
aio-libs:master
Jun 12, 2025
Merged

[pull] master from aio-libs:master#274
pull[bot] merged 1 commit intotj-python:masterfrom
aio-libs:master

Conversation

@pull
Copy link

@pull pull bot commented Jun 12, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

Bumps [pytest-cov](https://github.com/pytest-dev/pytest-cov) from 6.1.1
to 6.2.0.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest-cov/blob/master/CHANGELOG.rst">pytest-cov's
changelog</a>.</em></p>
<blockquote>
<h2>6.2.0 (2025-06-11)</h2>
<ul>
<li>
<p>The plugin now adds 3 rules in the filter warnings configuration to
prevent common coverage warnings being raised as obscure errors::</p>
<p>default:unclosed database in &lt;sqlite3.Connection object
at:ResourceWarning
once::PytestCovWarning
once::CoverageWarning</p>
<p>This fixes most of the bad interactions that are occurring on pytest
8.4 with <code>filterwarnings=error</code>.</p>
<p>The plugin will check if there already matching rules for the 3
categories
(<code>ResourceWarning</code>, <code>PytestCovWarning</code>,
<code>CoverageWarning</code>) and message (<code>unclosed database in
&lt;sqlite3.Connection object at</code>) before adding the filters.</p>
<p>This means you can have this in your pytest configuration for
complete oblivion (not recommended, if that is not clear)::</p>
<p>filterwarnings = [
&quot;error&quot;,
&quot;ignore:unclosed database in &lt;sqlite3.Connection object
at:ResourceWarning&quot;,
&quot;ignore::PytestCovWarning&quot;,
&quot;ignore::CoverageWarning&quot;,
]</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/dca5723086a00e8c145a84761b0ce810a8079892"><code>dca5723</code></a>
Bump version: 6.1.1 → 6.2.0</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/f69166a08444db4736c611cdc7746eeac9a2f158"><code>f69166a</code></a>
Also trigger the sqlite warning.</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/9dabad3f6baa8e3b66bb20e26ec65eabfbbbd604"><code>9dabad3</code></a>
Do not mess with the warnings if the plugin is disabled. Also, upgrade
to new...</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/222e991a8d6e39c4440ab85a1a8b621a6a03e608"><code>222e991</code></a>
Do some checks before adding the filters to allow users to silence these
warn...</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/ddc162b2bb175df13ba71184b6329dc8a6a0b1da"><code>ddc162b</code></a>
Update changelog.</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/22cc4e79190bc6cda738397a225b4a723934b5f7"><code>22cc4e7</code></a>
Bump.</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/5f6d020049045d42583b90cd6882713cc597b89b"><code>5f6d020</code></a>
Add some basic warnings configuration overrides for the common
offenders. Sho...</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/d2a2557d96b8526be2fd17eccd6bed352e2dbe65"><code>d2a2557</code></a>
Add latest xdist.</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/cc06ea33c6130d0c128128efe238530003a7425b"><code>cc06ea3</code></a>
Make this pass for now.</li>
<li><a
href="https://github.com/pytest-dev/pytest-cov/commit/b221fb1bfa5c90622881789a106a91ed9750a4f3"><code>b221fb1</code></a>
Add reproducer for <a
href="https://redirect.github.com/pytest-dev/pytest-cov/issues/693">#693</a>.</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest-cov/compare/v6.1.1...v6.2.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest-cov&package-manager=pip&previous-version=6.1.1&new-version=6.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@pull pull bot added the ⤵️ pull label Jun 12, 2025
@pull pull bot merged commit 7d56ed3 into tj-python:master Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants