[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-asyncio (changelog)	>=1.0.0,<1.1.0 → >=1.4.1,<1.5.0

---

Release Notes

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

v1.4.1: pytest-asyncio v1.4.1

Compare Source

1.4.1 - 2026-10-25

Added

• Declared support for Python 3.15 (#​1588)

Fixed

• Allow AsyncIterable as a return type for asynchronous generator fixtures decorated with pytest_asyncio.fixture (#​1090)

Notes for Downstream Packagers

• Source-tree development dependencies now use PEP 735 dependency groups and uv.lock. (#​1518)

v1.4.0: pytest-asyncio v1.4.0

Compare Source

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)

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 05:59 AM, only on Tuesday (* 0-5 * * 2)
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (v2@fe36ab6). Learn more about missing BASE report.

Additional details and impacted files

@@          Coverage Diff          @@
##             v2    #2357   +/-   ##
=====================================
  Coverage      ?   94.17%           
=====================================
  Files         ?      185           
  Lines         ?    13758           
  Branches      ?        0           
=====================================
  Hits          ?    12957           
  Misses        ?      801           
  Partials      ?        0           

Flag	Coverage Δ
unit	94.17% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.