ha-enthus1ast / plejd-mqtt-ha

Plejd MQTT
Apache License 2.0
1 stars 0 forks source link

Bump pytest-asyncio from 0.23.2 to 0.23.5 #46

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 7 months ago

Bumps pytest-asyncio from 0.23.2 to 0.23.5.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.5

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.

pytest-asyncio 0.23.5a0

0.23.5 (UNRELEASED)

  • Declare compatibility with pytest 8 #737
  • Fix typing errors with recent versions of mypy #769

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.4

0.23.4 (2024-01-28)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #729
  • Addresses further issues that caused an internal pytest error during test collection
  • Declares incompatibility with pytest 8 #737

pytest-asyncio 0.23.4a2

0.23.4 (UNRELEASED)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #729
  • Addresses further issues that caused an internal pytest error during test collection

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.4a1

0.23.4 (UNRELEASED)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #729

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.4a0

0.23.4 (UNRELEASED)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #729

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.3

0.23.3 (2024-01-01)

  • Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #706

... (truncated)

Commits
  • 3aef605 [build] Update actions/upload-artifact and actions/download-artifact to v4.
  • 4b1908d [fix] Prevent DeprecationWarning from bubbling to user code.
  • fc6d6cf Fix typing and update to mypy 1.8.0 (#769)
  • 6008cf1 Build(deps): Bump pluggy from 1.3.0 to 1.4.0 in /dependencies/default
  • 712c51b Build(deps): Bump coverage from 7.4.0 to 7.4.1 in /dependencies/default
  • 42fd304 Build(deps): Bump hypothesis in /dependencies/default
  • a40b4f6 Build(deps): Bump urllib3 from 2.1.0 to 2.2.0 in /dependencies/docs
  • 9d90f8e Build(deps): Bump certifi in /dependencies/docs
  • fe5da07 Build(deps): Bump markupsafe from 2.1.4 to 2.1.5 in /dependencies/docs
  • 42b140d fix compatibility with pytest ^8 (#776)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)
github-actions[bot] commented 7 months ago

šŸ¦™ MegaLinter status: āŒ ERROR

Descriptor Linter Files Fixed Errors Elapsed time
āœ… ACTION actionlint 3 0 0.03s
āœ… BASH bash-exec 1 0 0.01s
āœ… BASH shellcheck 1 0 0.02s
āœ… BASH shfmt 1 0 0 0.01s
āœ… DOCKERFILE hadolint 1 0 0.13s
āœ… JSON eslint-plugin-jsonc 2 0 0 1.47s
āœ… JSON jsonlint 2 0 0.23s
āœ… JSON prettier 2 0 0 0.38s
āœ… JSON v8r 2 0 2.65s
āš ļø MARKDOWN markdownlint 5 0 1 1.11s
āœ… MARKDOWN markdown-link-check 5 0 2.61s
āœ… MARKDOWN markdown-table-formatter 5 0 0 0.39s
āŒ PYTHON bandit 14 1 1.58s
āœ… PYTHON black 18 1 0 1.52s
āœ… PYTHON flake8 18 0 0.68s
āœ… PYTHON isort 18 1 0 0.34s
āœ… PYTHON pylint 18 0 13.18s
āœ… PYTHON ruff 18 1 0 0.04s
āœ… REPOSITORY gitleaks yes no 0.09s
āœ… REPOSITORY git_diff yes no 0.01s
āœ… REPOSITORY grype yes no 10.48s
āœ… REPOSITORY secretlint yes no 0.78s
āŒ REPOSITORY trivy yes 1 8.03s
āœ… REPOSITORY trivy-sbom yes no 2.52s
āœ… REPOSITORY trufflehog yes no 4.45s
āœ… SPELL lychee 14 0 0.65s
āœ… YAML prettier 7 0 0 0.7s
āœ… YAML v8r 7 0 7.46s
āœ… YAML yamllint 7 0 0.33s

See detailed report in MegaLinter reports

_MegaLinter is graciously provided by OX Security_

dependabot[bot] commented 6 months ago

Superseded by #51.