build(deps-dev): bump pytest-asyncio from 0.20.3 to 0.23.3

[dependabot]

Bumps pytest-asyncio from 0.20.3 to 0.23.3.

Release notes

Sourced from pytest-asyncio's releases.

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

pytest-asyncio 0.23.2

0.23.2 (2023-12-04)

• Fixes a bug that caused an internal pytest error when collecting .txt files #703

pytest-asyncio 0.23.1

0.23.1 (2023-12-03)

• Fixes a bug that caused an internal pytest error when using module-level skips #701

pytest-asyncio 0.23.0

This release is backwards-compatible with v0.21. Changes are non-breaking, unless you upgrade from v0.22.

• BREAKING: The asyncio_event_loop mark has been removed. Event loops with class, module, package, and session scopes can be requested via the scope keyword argument to the asyncio mark.
• Introduces the event_loop_policy fixture which allows testing with non-default or multiple event loops #662
• Introduces pytest_asyncio.is_async_test which returns whether a test item is managed by pytest-asyncio #376
• Removes and pytest-trio, mypy, and flaky from the test dependencies #620, #674, #678

pytest-asyncio 0.23.0b0

0.23.0 (UNRELEASED)

This release is backwards-compatible with v0.21. Changes are non-breaking, unless you upgrade from v0.22.

• BREAKING: The asyncio_event_loop mark has been removed. Event loops with class, module, package, and session scopes can be requested via the scope keyword argument to the asyncio mark.
• Introduces the event_loop_policy fixture which allows testing with non-default or multiple event loops #662
• Removes pytest-trio from the test dependencies #620

pytest-asyncio 0.23.0a1

... (truncated)

Commits

• 260b791 [docs] Prepare release of v0.23.3.
• 6a253e2 [docs] Shorten changelog by combining multiple issues.
• e2cbb90 [docs] Mention correct issue in changelog.
• 0c522bf [fix] Fixes a bug that caused an internal pytest error when using ImportWarni...
• 31c7e6f Build(deps): Bump coverage from 7.3.3 to 7.3.4 in /dependencies/default
• 38d5c7e Build(deps): Bump sphinx-rtd-theme in /dependencies/docs
• 650ec58 Build(deps): Bump babel from 2.13.1 to 2.14.0 in /dependencies/docs
• 0166a7e Build(deps): Bump typing-extensions in /dependencies/default
• 3a15f30 Build(deps): Bump coverage from 7.3.2 to 7.3.3 in /dependencies/default
• 28e91f0 Build(deps): Bump hypothesis in /dependencies/default
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.