chore(deps-dev): bump pytest-asyncio from 0.23.3 to 0.23.4 #83

New issue

Closed

opened 2025-10-14 16:05:58 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:05:58 -06:00

Owner

Originally created by @dependabot[bot] on 1/29/2024

Bumps pytest-asyncio from 0.23.3 to 0.23.4.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.4

0.23.4 (2024-01-28)

pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Addresses further issues that caused an internal pytest error during test collection

Declares incompatibility with pytest 8 #737

pytest-asyncio 0.23.4a2

0.23.4 (UNRELEASED)

pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Addresses further issues that caused an internal pytest error during test collection

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4a1

0.23.4 (UNRELEASED)

pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4a0

0.23.4 (UNRELEASED)

pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

Commits

b879130 [chore] Updated shed pre-commit hook to v2024.1.1.
a309bc5 [docs] Prepare release of v0.23.4.
c51c3e7 [docs] Mention compatibility issue with pytest 8.
dd129e9 [fix] Fixes a bug that prevented tests from being collected from package when...
463ce98 [fix] Avoid trying to install scoped event loops for unknown test collector t...
256ef7d [fix] pytest-asyncio no longer uses virtual modules to install dynamic packag...
8ba9bd0 [fix] Make virtual modules compatible with Windows.
df487d5 [ci] Shorten names of display OS in CI jobs.
9572f3e [tests] Fixed deprecated use of yield_fixture in test.
ef619b9 [build] Run tests on Windows.
Additional commits viewable in compare view

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 commands and options

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)

*Originally created by @dependabot[bot] on 1/29/2024* Bumps [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) from 0.23.3 to 0.23.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-asyncio/releases">pytest-asyncio's releases</a>.</em></p> <blockquote> <h2>pytest-asyncio 0.23.4</h2> <h1>0.23.4 (2024-01-28)</h1> <ul> <li>pytest-asyncio no longer imports additional, unrelated packages during test collection <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/729">#729</a></li> <li>Addresses further issues that caused an internal pytest error during test collection</li> <li>Declares incompatibility with pytest 8 <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/737">#737</a></li> </ul> <h2>pytest-asyncio 0.23.4a2</h2> <h1>0.23.4 (UNRELEASED)</h1> <ul> <li>pytest-asyncio no longer imports additional, unrelated packages during test collection <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/729">#729</a></li> <li>Addresses further issues that caused an internal pytest error during test collection</li> </ul> <h2>Known issues</h2> <p>As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706">#706</a>). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.</p> <h2>pytest-asyncio 0.23.4a1</h2> <h1>0.23.4 (UNRELEASED)</h1> <ul> <li>pytest-asyncio no longer imports additional, unrelated packages during test collection <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/729">#729</a></li> </ul> <h2>Known issues</h2> <p>As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706">#706</a>). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.</p> <h2>pytest-asyncio 0.23.4a0</h2> <h1>0.23.4 (UNRELEASED)</h1> <ul> <li>pytest-asyncio no longer imports additional, unrelated packages during test collection <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/729">#729</a></li> </ul> <h2>Known issues</h2> <p>As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706">#706</a>). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/b879130e3212884fde45f2ecfe48b41ce1eacce3"><code>b879130</code></a> [chore] Updated shed pre-commit hook to v2024.1.1.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/a309bc509b6a2010adadedba76c2a3ea8ca46676"><code>a309bc5</code></a> [docs] Prepare release of v0.23.4.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/c51c3e7cebfb5ffdeed6922e89bbf5259c45c8e3"><code>c51c3e7</code></a> [docs] Mention compatibility issue with pytest 8.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/dd129e9c4ce92cc8af50b82551e23ba2d857f8da"><code>dd129e9</code></a> [fix] Fixes a bug that prevented tests from being collected from package when...</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/463ce984677f0ac965f225c3b7ac14ebf43adad6"><code>463ce98</code></a> [fix] Avoid trying to install scoped event loops for unknown test collector t...</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/256ef7d2f5baab34d8668c6ffc476b7740b782fc"><code>256ef7d</code></a> [fix] pytest-asyncio no longer uses virtual modules to install dynamic packag...</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/8ba9bd03c44584929c7251cf1383df23f5e14f44"><code>8ba9bd0</code></a> [fix] Make virtual modules compatible with Windows.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/df487d5e2d7976c89f79d3459e7cb13c3899082e"><code>df487d5</code></a> [ci] Shorten names of display OS in CI jobs.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/9572f3e0e42d3359cbea5b70a02be6169059f0e8"><code>9572f3e</code></a> [tests] Fixed deprecated use of yield_fixture in test.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/ef619b9fea227a70387f1c97828cc21617c1ea2d"><code>ef619b9</code></a> [build] Run tests on Windows.</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-asyncio/compare/v0.23.3...v0.23.4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest-asyncio&package-manager=pip&previous-version=0.23.3&new-version=0.23.4)](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>