Skip to content

Commit 13e9477

Browse files
hauntsaninjaseifertm
authored andcommitted
Link to migration guides from changelog
1 parent 4d2cf3c commit 13e9477

File tree

2 files changed

+10
-0
lines changed

2 files changed

+10
-0
lines changed

docs/how-to-guides/migrate_from_0_23.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
.. _how_to_guides/migrate_from_0_23:
2+
13
========================================
24
How to migrate from pytest-asyncio v0.23
35
========================================

docs/reference/changelog.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,10 @@ Notes for Downstream Packagers
6262
`1.0.0 <https://github.com/pytest-dev/pytest-asyncio/tree/1.0.0>`_ - 2025-05-26
6363
===============================================================================
6464

65+
.. seealso::
66+
67+
:ref:`How to migrate from pytest-asyncio v0.23 <how_to_guides/migrate_from_0_23>`
68+
6569
Removed
6670
-------
6771

@@ -211,6 +215,10 @@ As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the t
211215
This release is backwards-compatible with v0.21.
212216
Changes are non-breaking, unless you upgrade from v0.22.
213217

218+
.. seealso::
219+
220+
:ref:`How to migrate from pytest-asyncio v0.21 <how_to_guides/migrate_from_0_21>`
221+
214222
- BREAKING: The *asyncio_event_loop* mark has been removed. Event loops with class, module, package, and session scopes can be requested via the *scope* keyword argument to the _asyncio_ mark.
215223
- Introduces the *event_loop_policy* fixture which allows testing with non-default or multiple event loops `#662 <https://github.com/pytest-dev/pytest-asyncio/pull/662>`_
216224
- Introduces ``pytest_asyncio.is_async_test`` which returns whether a test item is managed by pytest-asyncio `#376 <https://github.com/pytest-dev/pytest-asyncio/issues/376>`_

0 commit comments

Comments
 (0)