0.23.0 (UNRELEASED)

===================
This release is backwards-compatible with v0.21.
Changes are non-breaking, unless you upgrade from v0.22.

- 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.
- Introduces the *event_loop_policy* fixture which allows testing with non-default or multiple event loops  `pytest-dev#662 <https://github.com/pytest-dev/pytest-asyncio/pull/662>`_
- Removes pytest-trio from the test dependencies `pytest-dev#620 <https://github.com/pytest-dev/pytest-asyncio/pull/620>`_

* Class-scoped and module-scoped event loops can be requested

  via the _asyncio_event_loop_ mark. [pytest-dev#620](pytest-dev#620)
* Deprecate redefinition of the _event_loop_ fixture. (pytest-dev#587)[pytest-dev#531)
  Users requiring a class-scoped or module-scoped asyncio event loop for their tests
  should mark the corresponding class or module with _asyncio_event_loop_.
* Test items based on asynchronous generators always exit with _xfail_ status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. [pytest-dev#642](pytest-dev#642)
* Remove support for Python 3.7
* Declare support for Python 3.12

0.21.1 (2023-07-12)

===================
- Output a proper error message when an invalid ``asyncio_mode`` is selected.
- Extend warning message about unclosed event loops with additional possible cause.
  `pytest-dev#531 <https://github.com/pytest-dev/pytest-asyncio/issues/531>`_
- Previously, some tests reported "skipped" or "xfailed" as a result. Now all tests report a "success" result.

0.21.0 (23-03-19)

=================
- Drop compatibility with pytest 6.1. Pytest-asyncio now depends on pytest 7.0 or newer.
- pytest-asyncio cleans up any stale event loops when setting up and tearing down the
  event_loop fixture. This behavior has been deprecated and pytest-asyncio emits a
  DeprecationWarning when tearing down the event_loop fixture and current event loop
  has not been closed.

0.20.2 (22-11-11)

=================
- Fixes an issue with async fixtures that are defined as methods on a test class not being rebound to the actual test instance. `pytest-dev#197 <https://github.com/pytest-dev/pytest-asyncio/issues/197>`_
- Replaced usage of deprecated ``@pytest.mark.tryfirst`` with ``@pytest.hookimpl(tryfirst=True)`` `pytest-dev#438 <https://github.com/pytest-dev/pytest-asyncio/pull/438>`_

Release v0.20.1.

Release v0.20.0

Switch default mode to strict.