Skip to content

Commit 6e14cd2

Browse files
committed
chore: Prepare release of v1.4.0.
1 parent 4b900fb commit 6e14cd2

8 files changed

Lines changed: 40 additions & 12 deletions

File tree

changelog.d/1164.added.rst

Lines changed: 0 additions & 5 deletions
This file was deleted.

changelog.d/1298.changed.rst

Lines changed: 0 additions & 1 deletion
This file was deleted.

changelog.d/1394.changed.rst

Lines changed: 0 additions & 2 deletions
This file was deleted.

changelog.d/1395.downstream.rst

Lines changed: 0 additions & 1 deletion
This file was deleted.

changelog.d/1397.changed.rst

Lines changed: 0 additions & 1 deletion
This file was deleted.

changelog.d/1419.deprecated.rst

Lines changed: 0 additions & 1 deletion
This file was deleted.

changelog.d/724.fixed.rst

Lines changed: 0 additions & 1 deletion
This file was deleted.

docs/reference/changelog.rst

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,46 @@ This project uses `towncrier <https://towncrier.readthedocs.io/>`__ for changelo
1010

1111
.. towncrier release notes start
1212
13+
`1.4.0 <https://github.com/pytest-dev/pytest-asyncio/tree/1.4.0>`_ - 2026-05-26
14+
===============================================================================
15+
16+
Deprecated
17+
----------
18+
19+
- Overriding the *event_loop_policy* fixture is deprecated. Use the ``pytest_asyncio_loop_factories`` hook instead. (`#1419 <https://github.com/pytest-dev/pytest-asyncio/issues/1419>`_)
20+
21+
22+
Added
23+
-----
24+
25+
- Added the ``pytest_asyncio_loop_factories`` hook to parametrize asyncio tests with custom event loop factories.
26+
27+
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.
28+
29+
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 <https://github.com/pytest-dev/pytest-asyncio/issues/1164>`_)
30+
31+
32+
Changed
33+
-------
34+
35+
- Improved the readability of the warning message that is displayed when ``asyncio_default_fixture_loop_scope`` is unset (`#1298 <https://github.com/pytest-dev/pytest-asyncio/issues/1298>`_)
36+
- Only import ``asyncio.AbstractEventLoopPolicy`` for type checking to avoid raising
37+
a DeprecationWarning. (`#1394 <https://github.com/pytest-dev/pytest-asyncio/issues/1394>`_)
38+
- Updated minimum supported pytest version to v8.4.0. (`#1397 <https://github.com/pytest-dev/pytest-asyncio/issues/1397>`_)
39+
40+
41+
Fixed
42+
-----
43+
44+
- 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 <https://github.com/pytest-dev/pytest-asyncio/issues/724>`_)
45+
46+
47+
Notes for Downstream Packagers
48+
------------------------------
49+
50+
- Added dependency on ``sphinx-tabs >= 3.5`` to organize documentation examples into tabs. (`#1395 <https://github.com/pytest-dev/pytest-asyncio/issues/1395>`_)
51+
52+
1353
`1.3.0 <https://github.com/pytest-dev/pytest-asyncio/tree/1.3.0>`_ - 2025-11-10
1454
===============================================================================
1555

0 commit comments

Comments
 (0)