Bump pytest-asyncio from 1.1.0 to 1.2.0

[dependabot]

Bumps pytest-asyncio from 1.1.0 to 1.2.0.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 1.2.0

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.

pytest-asyncio 1.1.1

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)

Commits

• 0d3988f ci: Create GitHub release before publishing to PyPI.
• 07c5a0b docs: Include orphaned news fragment in changelog.
• be24582 chore: Prepare release of v1.2.0.
• 7aeb296 docs: Streamline news fragments
• 7b8311c ci: Fixes a bug that prevented SSH signature from being stripped from release...
• 9d4c2bd docs: Add changelog entry for Pyright compatibility.
• 94f6106 test: Added tests which assert that the event loop is reinstated if unset by ...
• df61991 [pre-commit.ci] pre-commit autoupdate
• f1f7941 Build(deps): Bump pytest from 8.4.1 to 8.4.2
• c77d3d3 Build(deps): Bump twine from 6.1.0 to 6.2.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[llucax]

Issues with pytest_min because we need to bump typing_extensions:

The conflict is caused by:
    The user requested typing-extensions==4.6.0
    frequenz-channels 0.0.post1+g5fed73e depends on typing-extensions<5 and >=4.6.0
    frequenz-channels[dev-pytest] 0.0.post1+g5fed73e depends on typing-extensions<5 and >=4.6.0
    pytest-asyncio 1.2.0 depends on typing-extensions>=4.12; python_version < "3.13"

[llucax]

Added commit, this needs someone else's approval now.

[llucax]

While looking into the failure here, I noticed that the pytest_min session doesn't install the minimum declared dependencies for everything it installs, only for the production project.dependencies. So all development dependencies are still used at the highest version possible (for example pytest, pytest-asyncio, pylint, etc.). I guess this could cause some issues, mixing old and new dependencies, or at least explain why I saw some dev dependencies that are actually higher than the deps declared in pyproject.toml.