chore(deps): update dependency pytest-asyncio to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-asyncio (changelog)	==0.23.8 → ==1.3.0

---

Release Notes

pytest-dev/pytest-asyncio (pytest-asyncio)

v1.3.0: pytest-asyncio 1.3.0

Compare Source

1.3.0 - 2025-11-10

Removed

• Support for Python 3.9 (#​1278)

Added

• Support for pytest 9 (#​1279)

Notes for Downstream Packagers

• Tested Python versions include free threaded Python 3.14t (#​1274)
• Tests are run in the same pytest process, instead of spawning a subprocess with pytest.Pytester.runpytest_subprocess. This prevents the test suite from accidentally using a system installation of pytest-asyncio, which could result in test errors. (#​1275)

v1.2.0: pytest-asyncio 1.2.0

Compare Source

1.2.0 - 2025-09-12

Added

• --asyncio-debug CLI option and asyncio_debug configuration option to enable asyncio debug mode for the default event loop. (#​980)
• A pytest.UsageError for invalid configuration values of asyncio_default_fixture_loop_scope and asyncio_default_test_loop_scope. (#​1189)
• Compatibility with the Pyright type checker (#​731)

Fixed

• RuntimeError: There is no current event loop in thread 'MainThread' when any test unsets the event loop (such as when using asyncio.run and asyncio.Runner). (#​1177)
• Deprecation warning when decorating an asynchronous fixture with @pytest.fixture in [strict]{.title-ref} mode. The warning message now refers to the correct package. (#​1198)

Notes for Downstream Packagers

• Bump the minimum required version of tox to v4.28. This change is only relevant if you use the tox.ini file provided by pytest-asyncio to run tests.
• Extend dependency on typing-extensions>=4.12 from Python<3.10 to Python<3.13.

v1.1.1: pytest-asyncio 1.1.1

Compare Source

v1.1.1 - 2025-09-12

Notes for Downstream Packagers

- Addresses a build problem with setuptoos-scm >= 9 caused by invalid setuptools-scm configuration in pytest-asyncio. (#​1192)

v1.1.0: pytest-asyncio 1.1.0

Compare Source

Added

• Propagation of ContextVars from async fixtures to other fixtures and tests on Python 3.10 and older (#​127)
• Cancellation of tasks when the loop_scope ends (#​200)
• Warning when the current event loop is closed by a test

Fixed

• Error about missing loop when calling functions requiring a loop in the finally clause of a task (#​878)
• An error that could cause duplicate warnings to be issued

Notes for Downstream Packagers

• Added runtime dependency on backports.asyncio.runner for use with Python 3.10 and older

v1.0.0: pytest-asyncio 1.0.0

Compare Source

1.0.0 - 2025-05-26

Removed

• The deprecated event_loop fixture.
  (#​1106)

Added

• Prelimiary support for Python 3.14
  (#​1025)

Changed

• Scoped event loops (e.g. module-scoped loops) are created once rather
  than per scope (e.g. per module). This reduces the number of fixtures
  and speeds up collection time, especially for large test suites.
  (#​1107)
• The loop_scope argument to pytest.mark.asyncio no longer forces
  that a pytest Collector exists at the level of the specified scope.
  For example, a test function marked with
  pytest.mark.asyncio(loop_scope="class") no longer requires a class
  surrounding the test. This is consistent with the behavior of the
  scope argument to pytest_asyncio.fixture.
  (#​1112)

Fixed

• An error caused when using pytest's [--setup-plan]{.title-ref}
  option.
  (#​630)
• Unsuppressed import errors with pytest option
  --doctest-ignore-import-errors
  (#​797)
• A "fixture not found" error in connection with package-scoped loops
  (#​1052)

Notes for Downstream Packagers

• Removed a test that had an ordering dependency on other tests.
  (#​1114)

v0.26.0: pytest-asyncio 0.26.0

Compare Source

• Adds configuration option that sets default event loop scope for all tests #​793
• Improved type annotations for pytest_asyncio.fixture #​1045
• Added typing-extensions as additional dependency for Python <3.10 #​1045

v0.25.3: pytest-asyncio 0.25.3

Compare Source

• Avoid errors in cleanup of async generators when event loop is already closed #​1040

v0.25.2: pytest-asyncio 0.25.2

Compare Source

• Call loop.shutdown_asyncgens() before closing the event loop to ensure async generators are closed in the same manner as asyncio.run does #​1034

v0.25.1: pytest-asyncio 0.25.1

Compare Source

• 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

v0.25.0: pytest-asyncio 0.25.0

Compare Source

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

v0.24.0: pytest-asyncio 0.24.0

Compare Source

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package pytest-asyncio
Using CPython 3.14.3 interpreter at: /opt/containerbase/tools/python/3.14.3/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.9.*'):
  ╰─▶ Because the requested Python version (>=3.8) does not satisfy
      Python>=3.10 and pytest-asyncio==1.3.0 depends on Python>=3.10, we can
      conclude that pytest-asyncio==1.3.0 cannot be used.
      And because workos:dev depends on pytest-asyncio==1.3.0 and your project
      requires workos:dev, we can conclude that your project's requirements
      are unsatisfiable.

      hint: While the active Python version is 3.14, the resolution failed for
      other Python versions supported by your project. Consider limiting your
      project's supported Python versions using `requires-python`.

      hint: The `requires-python` value (>=3.8) includes Python versions that
      are not supported by your dependencies (e.g., pytest-asyncio==1.3.0 only
      supports >=3.10). Consider using a more restrictive `requires-python`
      value (like >=3.10).

[greptile-apps]

Greptile Overview

Greptile Summary

Updated pytest-asyncio from 0.23.8 to 1.3.0, a major version bump that includes:

• Dropped support for Python 3.9
• Added support for pytest 9
• Removed the deprecated event_loop fixture (v1.0.0)
• Added new features like --asyncio-debug CLI option and task cancellation when loop scope ends

Compatibility Assessment:

This codebase supports Python >=3.8 (as defined in pyproject.toml:8), but pytest-asyncio 1.3.0 dropped Python 3.9 support. The current codebase uses:

• @pytest.mark.asyncio decorator on test classes and methods
• Standard pytest fixtures (no custom event_loop fixture)
• No deprecated scope parameter usage

The upgrade is compatible with the test suite's usage patterns. All async tests use the standard @pytest.mark.asyncio marker without relying on the removed event_loop fixture.

Confidence Score: 4/5

• Safe to merge with one consideration about Python version compatibility
• The dependency update from pytest-asyncio 0.23.8 to 1.3.0 is straightforward. No breaking changes affect this codebase since it doesn't use the deprecated event_loop fixture. However, there's a Python version compatibility concern: the project supports Python >=3.8, but pytest-asyncio 1.3.0 dropped support for Python 3.9. Since the minimum Python version is 3.8 (which is lower than 3.9), tests may fail on Python 3.8 and 3.9 environments.
• Check pyproject.toml for Python version alignment with pytest-asyncio 1.3.0 requirements

Important Files Changed

Filename	Overview
pyproject.toml	Updated pytest-asyncio from 0.23.8 to 1.3.0, a major version bump with no breaking changes affecting this codebase

_{Last reviewed commit: b7a56e8}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

pyproject.toml
Python version compatibility issue: requires-python = ">=3.8" conflicts with pytest-asyncio==1.3.0 which dropped Python 3.9 support (meaning it now requires Python 3.10+). Tests will fail on Python 3.8 and 3.9. Either update this to requires-python = ">=3.10" or pin pytest-asyncio to a version that supports Python 3.8/3.9.