dependabot[bot] opened a new pull request, #1706:
URL: https://github.com/apache/plc4x/pull/1706

   Bumps [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) from 
0.23.7 to 0.23.8.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/pytest-dev/pytest-asyncio/releases";>pytest-asyncio's 
releases</a>.</em></p>
   <blockquote>
   <h2>pytest-asyncio 0.23.8</h2>
   <h1>0.23.8 (2024-07-17)</h1>
   <ul>
   <li>Fixes a bug that caused duplicate markers in async tests <a 
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/813";>#813</a></li>
   </ul>
   <h2>Known issues</h2>
   <p>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 <a 
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706";>#706</a>).
 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.</p>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/4be86a5174f864f6098872fc9fdf0a557a1b50f8";><code>4be86a5</code></a>
 docs: Prepare release of v0.23.8.</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/74b3a0a2057b6faaaf2dfc2d1de785abcf145bcb";><code>74b3a0a</code></a>
 Build(deps): Bump exceptiongroup in /dependencies/default</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/b0009ca36ad66ec0bf40b2ad97edaa96fa39e510";><code>b0009ca</code></a>
 [build] Declare support for Python 3.13.</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/c747c7db7837d7cb7fef029af92092e20759e217";><code>c747c7d</code></a>
 Build(deps): Bump coverage from 7.5.4 to 7.6.0 in /dependencies/default</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/5c40a1cf8b6f47f47596fcf1117420585517c627";><code>5c40a1c</code></a>
 Build(deps): Bump hypothesis in /dependencies/default</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/b735e8a8ef3118109521c7b058596cf7decb03d0";><code>b735e8a</code></a>
 build: Remove development dependency on Docker.</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/91171b41c2bd6714955cd3d72e07bd9091f909e2";><code>91171b4</code></a>
 ci: Test with CPython 3.13.</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/d572138e097f493c07c84151649d191df5e09ee0";><code>d572138</code></a>
 Build(deps): Bump hypothesis in /dependencies/default</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/a89e4d7a899d7587e1efa6cafe9e181b3e2a1d69";><code>a89e4d7</code></a>
 Build(deps): Bump certifi in /dependencies/docs</li>
   <li><a 
href="https://github.com/pytest-dev/pytest-asyncio/commit/b646cc18a222c8043433c38a42c07245fe9735ce";><code>b646cc1</code></a>
 [fix] Fixed a bug that causes markers to be duplicated for async test 
functions.</li>
   <li>Additional commits viewable in <a 
href="https://github.com/pytest-dev/pytest-asyncio/compare/v0.23.7...v0.23.8";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest-asyncio&package-manager=pip&previous-version=0.23.7&new-version=0.23.8)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@plc4x.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to