Update pytest-asyncio requirement from >=0.24.0 to >=1.4.0

[dependabot]

Updates the requirements on pytest-asyncio to permit the latest version.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio v1.4.0

1.4.0 - 2026-05-26

Deprecated

• Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#1419)

Added

• Added the pytest_asyncio_loop_factories hook to parametrize asyncio tests with custom event loop factories.

  The hook returns a mapping of factory names to loop factories, and pytest.mark.asyncio(loop_factories=[...]) selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.

  Synchronous @pytest_asyncio.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#1164)

Changed

• Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#1298)
• Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising a DeprecationWarning. (#1394)
• Updated minimum supported pytest version to v8.4.0. (#1397)

Fixed

• Fixed a ResourceWarning: unclosed event loop warning that could occur when a synchronous test called asyncio.run() or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (#724)

Notes for Downstream Packagers

• Added dependency on sphinx-tabs >= 3.5 to organize documentation examples into tabs. (#1395)

Commits

• 6e14cd2 chore: Prepare release of v1.4.0.
• 4b900fb Build(deps): Bump codecov/codecov-action from 6.0.0 to 6.0.1
• ab9f632 Build(deps): Bump zipp from 3.23.1 to 4.1.0
• a56fc77 Build(deps): Bump hypothesis from 6.152.6 to 6.152.8
• e8bae9b Build(deps): Bump requests from 2.34.0 to 2.34.2
• fc43340 Build(deps): Bump idna from 3.14 to 3.15
• 762eaf5 Build(deps): Bump jaraco-functools from 4.4.0 to 4.5.0
• b62e222 Build(deps): Bump click from 8.3.3 to 8.4.0
• 9190447 Build(deps): Bump pydantic from 2.13.3 to 2.13.4
• 82a393c ci: Remove unnecessary debug output.
• 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 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)

[codeowners-service-app]

Assigned NoahStapp for team dbx-python because blink1073 is out of office.

[sleepyStick]

i don't think we can do this one at the moment given that we still support python3.9:

[2026/07/24 12:23:13.243] Creating virtual environment at: .venv
[2026/07/24 12:23:13.313] × No solution found when resolving dependencies for split (markers:
[2026/07/24 12:23:13.313] │ python_full_version > '3.9' and python_full_version < '3.10'):
[2026/07/24 12:23:13.313] ╰─▶ Because the requested Python version (>=3.9) does not satisfy
[2026/07/24 12:23:13.313] Python>=3.10 and pytest-asyncio==1.4.0 depends on Python>=3.10, we can
[2026/07/24 12:23:13.313] conclude that pytest-asyncio==1.4.0 cannot be used.
[2026/07/24 12:23:13.313] And because only pytest-asyncio<=1.4.0 is available, we can conclude
[2026/07/24 12:23:13.313] that pytest-asyncio>=1.4.0 cannot be used.
[2026/07/24 12:23:13.313] And because pymongo[test] depends on pytest-asyncio>=1.4.0 and your
[2026/07/24 12:23:13.313] project requires pymongo[test], we can conclude that your project's
[2026/07/24 12:23:13.313] requirements are unsatisfiable.
[2026/07/24 12:23:13.313] hint: The requires-python value (>=3.9) includes Python versions that
[2026/07/24 12:23:13.313] are not supported by your dependencies (e.g., pytest-asyncio==1.4.0 only
[2026/07/24 12:23:13.313] supports >=3.10). Consider using a more restrictive requires-python
[2026/07/24 12:23:13.313] value (like >=3.10).
[2026/07/24 12:23:13.313] hint: While the active Python version is 3.10, the resolution failed for
[2026/07/24 12:23:13.313] other Python versions supported by your project. Consider limiting your
[2026/07/24 12:23:13.313] project's supported Python versions using requires-python.