chore(deps-dev): bump the development-dependencies group with 2 updates

[dependabot[bot]]

Bumps the development-dependencies group with 2 updates: nonebug and pytest-asyncio.

Updates nonebug from 0.3.5 to 0.3.6

Release notes

Sourced from nonebug's releases.

Release 0.3.6

What's Changed

• Feature: 适配 Pydantic V2 并放宽 pytest 限制 by @​he0119 in nonebot/nonebug#22

Full Changelog: https://github.com/nonebot/nonebug/compare/v0.3.5...v0.3.6

Commits

• 20f70a4 :bookmark: bump version 0.3.6
• 1cec9ad :sparkles: Feature: 适配 Pydantic V2 并放宽 pytest 限制 (#22)
• 80cce51 :arrow_up: auto update by pre-commit hooks (#21)
• 552518d :arrow_up: auto update by pre-commit hooks (#20)
• 48d8c54 :arrow_up: auto update by pre-commit hooks (#19)
• 0eb2ed6 :arrow_up: auto update by pre-commit hooks (#18)
• 866166d :arrow_up: auto update by pre-commit hooks (#17)
• 6345a32 :arrow_up: auto update by pre-commit hooks (#16)
• 3229fb6 :construction_worker: use trusted publisher
• See full diff in compare view

Updates pytest-asyncio from 0.23.5 to 0.23.6

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.6

0.23.6 (2024-03-19)

• Fix compatibility with pytest 8.2 #800

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.5.post1

0.23.5 (2024-02-09)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769
• Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

Commits

• c34da04 [docs] Mentioned pytest 8.2 compatibility fix in changelog.
• 143f745 Fix compatibility with pytest 8.2 FixtureDef.unittest removal
• 13d4b79 Remove unused function _removesuffix
• cdd2c49 Use FixtureRequest instead of SubRequest
• c3429fa Build(deps): Bump packaging from 23.2 to 24.0 in /dependencies/docs
• 5f2338d Build(deps): Bump pypa/gh-action-pypi-publish from 1.8.12 to 1.8.14
• 726c6e0 Build(deps): Bump coverage from 7.4.3 to 7.4.4 in /dependencies/default
• 8bd8288 Build(deps): Bump pytest from 8.0.2 to 8.1.1 in /dependencies/default
• ef3b347 Build(deps): Bump packaging from 23.2 to 24.0 in /dependencies/default
• b22d84e [docs] Fixes the example showing how to run all tests in a session-scoped loop.
• 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (521c4e8) to head (5a09909). Report is 1 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #205 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 12 12 Lines 654 654 ========================================= Hits 654 654 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[dependabot[bot]]

Looks like these dependencies are updatable in another way, so this is no longer needed.