search

long2ice / meilisync

Realtime sync data from MySQL/PostgreSQL/MongoDB to Meilisearch
https://github.com/long2ice/meilisync
Apache License 2.0
285 stars 43 forks source link

chore(deps-dev): bump pytest-asyncio from 0.23.3 to 0.23.4 #78

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 9 months ago

Bumps pytest-asyncio from 0.23.3 to 0.23.4.

Release notes

Sourced from pytest-asyncio's releases.

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.

Commits
  • b879130 [chore] Updated shed pre-commit hook to v2024.1.1.
  • a309bc5 [docs] Prepare release of v0.23.4.
  • c51c3e7 [docs] Mention compatibility issue with pytest 8.
  • dd129e9 [fix] Fixes a bug that prevented tests from being collected from package when...
  • 463ce98 [fix] Avoid trying to install scoped event loops for unknown test collector t...
  • 256ef7d [fix] pytest-asyncio no longer uses virtual modules to install dynamic packag...
  • 8ba9bd0 [fix] Make virtual modules compatible with Windows.
  • df487d5 [ci] Shorten names of display OS in CI jobs.
  • 9572f3e [tests] Fixed deprecated use of yield_fixture in test.
  • ef619b9 [build] Run tests on Windows.
  • 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)
dependabot[bot] commented 9 months ago

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.

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