chore(deps-dev): bump pytest-asyncio from 0.26.0 to 1.0.0

[dependabot]

Bumps pytest-asyncio from 0.26.0 to 1.0.0.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 1.0.0

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)

pytest-asyncio 1.0.0a1

1.0.0a1 - 2025-05-09

Removed

• The deprecated event_loop fixture. (#1106)

... (truncated)

Commits

• 5ef97bd chore: Prepare release of v1.0.0.
• f212e24 docs: Mention fix of #797.
• 32c1d10 test: Removed obsolete test for async_gen_fixtures.
• 627ce92 [pre-commit.ci] pre-commit autoupdate
• a55ff36 Build(deps): Bump pluggy from 1.5.0 to 1.6.0 in /dependencies/default
• 633389f Build(deps): Bump hypothesis in /dependencies/default
• 0c99466 docs: Fixed an error that reported a missing event_loop fixture when using pa...
• 0688d17 ci: Replace Github template expansion with env variable expansion.
• 2adcf52 ci: Quote Github variable expansion.
• dd0fac9 ci: Fixed a bug that prevented release notes from being extracted from a Git ...
• 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)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.