chore(deps): update dev dependencies (master) (major)

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-asyncio (changelog)	^0.25.0 -> ^1.0.0
pytest-cov (changelog)	^6.0.0 -> ^7.0.0

---

Release Notes

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

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

v1.0.0: pytest-asyncio 1.0.0

Compare Source

1.0.0 - 2025-05-26

Removed

• The deprecated event_loop fixture.
  (#​1106)

Added

• Prelimiary support for Python 3.14
  (#​1025)

Changed

• Scoped event loops (e.g. module-scoped loops) are created once rather
  than per scope (e.g. per module). This reduces the number of fixtures
  and speeds up collection time, especially for large test suites.
  (#​1107)
• The loop_scope argument to pytest.mark.asyncio no longer forces
  that a pytest Collector exists at the level of the specified scope.
  For example, a test function marked with
  pytest.mark.asyncio(loop_scope="class") no longer requires a class
  surrounding the test. This is consistent with the behavior of the
  scope argument to pytest_asyncio.fixture.
  (#​1112)

Fixed

• An error caused when using pytest's [--setup-plan]{.title-ref}
  option.
  (#​630)
• Unsuppressed import errors with pytest option
  --doctest-ignore-import-errors
  (#​797)
• A "fixture not found" error in connection with package-scoped loops
  (#​1052)

Notes for Downstream Packagers

• Removed a test that had an ordering dependency on other tests.
  (#​1114)

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

pytest-dev/pytest-cov (pytest-cov)

v7.0.0

Compare Source

• Dropped support for subprocesses measurement.

  It was a feature added long time ago when coverage lacked a nice way to measure subprocesses created in tests.
  It relied on a .pth file, there was no way to opt-out and it created bad interations
  with coverage's new patch system <https://coverage.readthedocs.io/en/latest/config.html#run-patch>_ added
  in 7.10 <https://coverage.readthedocs.io/en/7.10.6/changes.html#version-7-10-0-2025-07-24>_.

  To migrate to this release you might need to enable the suprocess patch, example for .coveragerc:

  .. code-block:: ini

  [run]
  patch = subprocess

  This release also requires at least coverage 7.10.6.

• Switched packaging to have metadata completely in pyproject.toml and use hatchling <https://pypi.org/project/hatchling/>_ for
  building.
  Contributed by Ofek Lev in #&#8203;551 <https://github.com/pytest-dev/pytest-cov/pull/551>_
  with some extras in #&#8203;716 <https://github.com/pytest-dev/pytest-cov/pull/716>_.

• Removed some not really necessary testing deps like six.

v6.3.0

Compare Source

• Added support for markdown reports.
  Contributed by Marcos Boger in #&#8203;712 <https://github.com/pytest-dev/pytest-cov/pull/712>_
  and #&#8203;714 <https://github.com/pytest-dev/pytest-cov/pull/714>_.
• Fixed some formatting issues in docs.
  Anonymous contribution in #&#8203;706 <https://github.com/pytest-dev/pytest-cov/pull/706>_.

v6.2.1

Compare Source

• Added a version requirement for pytest's pluggy dependency (1.2.0, released 2023-06-21) that has the required new-style hookwrapper API.

• Removed deprecated license classifier (packaging).

• Disabled coverage warnings in two more situations where they have no value:

  • "module-not-measured" in workers
  • "already-imported" in subprocesses

v6.2.0

Compare Source

• The plugin now adds 3 rules in the filter warnings configuration to prevent common coverage warnings being raised as obscure errors::

  default:unclosed database in <sqlite3.Connection object at:ResourceWarning
  once::PytestCovWarning
  once::CoverageWarning

  This fixes most of the bad interactions that are occurring on pytest 8.4 with filterwarnings=error.

  The plugin will check if there already matching rules for the 3 categories
  (ResourceWarning, PytestCovWarning, CoverageWarning) and message (unclosed database in <sqlite3.Connection object at) before adding the filters.

  This means you can have this in your pytest configuration for complete oblivion (not recommended, if that is not clear)::

  filterwarnings = [
  "error",
  "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning",
  "ignore::PytestCovWarning",
  "ignore::CoverageWarning",
  ]

v6.1.1

Compare Source

• Fixed breakage that occurs when --cov-context and the no_cover marker are used together.

v6.1.0

Compare Source

• Change terminal output to use full width lines for the coverage header.
  Contributed by Tsvika Shapira in #&#8203;678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.
• Removed unnecessary CovFailUnderWarning. Fixes #&#8203;675 <https://github.com/pytest-dev/pytest-cov/issues/675>_.
• Fixed the term report not using the precision specified via --cov-precision.

---

Configuration

📅 Schedule: Branch creation - "every 4th week on Thursday before 10am" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.