build(deps-dev): bump pytest-asyncio from 0.23.8 to 0.25.1

[dependabot]

Bumps pytest-asyncio from 0.23.8 to 0.25.1.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.25.1

• Fixes an issue that caused a broken event loop when a function-scoped test was executed in between two tests with wider loop scope #950
• Improves test collection speed in auto mode #1020
• Corrects the warning that is emitted upon redefining the event_loop fixture

pytest-asyncio 0.25.0

0.25.0 (2024-12-13)

• Deprecated: Added warning when asyncio test requests async @pytest.fixture in strict mode. This will become an error in a future version of flake8-asyncio. #979
• Updates the error message about pytest.mark.asyncio's scope keyword argument to say loop_scope instead. #1004
• Verbose log displays correct parameter name: asyncio_default_fixture_loop_scope #990
• Propagates contextvars set in async fixtures to other fixtures and tests on Python 3.11 and above. #1008

pytest-asyncio 0.24.0

0.24.0 (2024-08-22)

• BREAKING: Updated minimum supported pytest version to v8.2.0
• Adds an optional loop_scope keyword argument to pytest.mark.asyncio. This argument controls which event loop is used to run the marked async test. #706, #871
• Deprecates the optional scope keyword argument to pytest.mark.asyncio for API consistency with pytest_asyncio.fixture. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.
• Raises an error when passing scope or loop_scope as a positional argument to @pytest.mark.asyncio. #812
• Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules #862 #668

pytest-asyncio 0.24.0a1

0.24.0 (UNRELEASED)

• BREAKING: Updated minimum supported pytest version to v8.2.0
• Adds an optional loop_scope keyword argument to pytest.mark.asyncio. This argument controls which event loop is used to run the marked async test. #706, #871
• Deprecates the optional scope keyword argument to pytest.mark.asyncio for API consistency with pytest_asyncio.fixture. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.
• Raises an error when passing scope or loop_scope as a positional argument to @pytest.mark.asyncio. #812
• Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules #862 #668

pytest-asyncio 0.24.0a0

0.24.0 (UNRELEASED)

• Adds an optional loop_scope keyword argument to pytest.mark.asyncio. This argument controls which event loop is used to run the marked async test. #706, #871
• Deprecates the optional scope keyword argument to pytest.mark.asyncio for API consistency with pytest_asyncio.fixture. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.
• Raises an error when passing scope or loop_scope as a positional argument to @pytest.mark.asyncio. #812

Commits

• 623ab74 docs: Prepare release of v0.25.1.
• c236550 docs: Fix broken link to the pytest.mark.asyncio reference.
• 41c645b fix: Correct warning message when redefining the event_loop fixture.
• 2fd10f8 docs: Clarify deprecation of event_loop fixture.
• a4e82ab docs: Added changelog entry for #1020.
• 04f9044 refactor: Replace the "__original_fixture_loop" magic attribute with the more...
• dafef6c refactor: Extracted a function to mark an event loop as created by pytest-asy...
• 0c931b7 refactor: Extracted function to check if a loop was created by pytest-asyncio.
• 0642dcd fix: Fix broken event loop when a function-scoped test is in between two wide...
• 050a5f8 [pre-commit.ci] pre-commit autoupdate
• 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)