chore(deps): update dependency pytest-asyncio to v0.26.0

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

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.8.*'):
  ╰─▶ Because the requested Python version (>=3.8) does not satisfy
      Python>=3.9 and pytest-asyncio==0.26.0 depends on Python>=3.9, we can
      conclude that pytest-asyncio==0.26.0 cannot be used.
      And because workos:dev depends on pytest-asyncio==0.26.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==0.26.0
      only supports >=3.9). Consider using a more restrictive
      `requires-python` value (like >=3.9).

[greptile-apps]

Greptile Overview

Greptile Summary

Updates the pytest-asyncio pinned version used in the test dependency group from 0.23.8 to 0.26.0 in pyproject.toml. This affects only the test environment tooling and does not change runtime package dependencies or library code paths.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• Change is a single pinned dev/test dependency update in pyproject.toml with no code modifications; failure mode is limited to tests breaking, which CI should catch.
• No files require special attention

Important Files Changed

Filename	Overview
pyproject.toml	Bumps test dependency pytest-asyncio from 0.23.8 to 0.26.0 in the [dependency-groups].test section; no other changes.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer/CI
    participant UV as uv/pip resolver
    participant Pytest as pytest
    participant PA as pytest-asyncio plugin

    Dev->>UV: Install dependency-group "test"
    UV-->>Dev: pytest==8.3.4 + pytest-asyncio==0.26.0
    Dev->>Pytest: Run test suite
    Pytest->>PA: Load plugin & configure asyncio mode/loop scope
    PA-->>Pytest: Provide asyncio fixtures/markers
    Pytest-->>Dev: Execute async tests

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}