Bump the actions group with 1 update

[dependabot]

Bumps the actions group with 1 update: pytest-asyncio.

Updates pytest-asyncio from 0.23.2 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.

pytest-asyncio 0.23.3

0.23.3 (2024-01-01)

• Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #706
• Fixes various bugs that caused an internal pytest error during test collection #711 #713 #719

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.3a0

0.23.3 (UNRELEASED)

• Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #708
• Fixes a bug that caused an internal pytest error when using unittest.SkipTest in a module #711

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions