dependabot[bot] opened a new pull request, #1736: URL: https://github.com/apache/plc4x/pull/1736
Bumps [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) from 0.23.8 to 0.24.0. <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.24.0</h2> <h1>0.24.0 (2024-08-22)</h1> <ul> <li>BREAKING: Updated minimum supported pytest version to v8.2.0</li> <li>Adds an optional <em>loop_scope</em> keyword argument to <em>pytest.mark.asyncio</em>. This argument controls which event loop is used to run the marked async test. <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706";>#706</a>, <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/pull/871";>#871</a></li> <li>Deprecates the optional <em>scope</em> keyword argument to <em>pytest.mark.asyncio</em> for API consistency with <code>pytest_asyncio.fixture</code>. Users are encouraged to use the <em>loop_scope</em> keyword argument, which does exactly the same.</li> <li>Raises an error when passing <em>scope</em> or <em>loop_scope</em> as a positional argument to <code>@pytest.mark.asyncio</code>. <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/812";>#812</a></li> <li>Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/862";>#862</a> <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/668";>#668</a></li> </ul> <h2>pytest-asyncio 0.24.0a1</h2> <h1>0.24.0 (UNRELEASED)</h1> <ul> <li>BREAKING: Updated minimum supported pytest version to v8.2.0</li> <li>Adds an optional <em>loop_scope</em> keyword argument to <em>pytest.mark.asyncio</em>. This argument controls which event loop is used to run the marked async test. <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706";>#706</a>, <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/pull/871";>#871</a></li> <li>Deprecates the optional <em>scope</em> keyword argument to <em>pytest.mark.asyncio</em> for API consistency with <code>pytest_asyncio.fixture</code>. Users are encouraged to use the <em>loop_scope</em> keyword argument, which does exactly the same.</li> <li>Raises an error when passing <em>scope</em> or <em>loop_scope</em> as a positional argument to <code>@pytest.mark.asyncio</code>. <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/812";>#812</a></li> <li>Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/862";>#862</a> <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/668";>#668</a></li> </ul> <h2>pytest-asyncio 0.24.0a0</h2> <h1>0.24.0 (UNRELEASED)</h1> <ul> <li>Adds an optional <em>loop_scope</em> keyword argument to <em>pytest.mark.asyncio</em>. This argument controls which event loop is used to run the marked async test. <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706";>#706</a>, <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/871";>#871</a></li> <li>Deprecates the optional <em>scope</em> keyword argument to <em>pytest.mark.asyncio</em> for API consistency with <code>pytest_asyncio.fixture</code>. Users are encouraged to use the <em>loop_scope</em> keyword argument, which does exactly the same.</li> <li>Raises an error when passing <em>scope</em> or <em>loop_scope</em> as a positional argument to <code>@pytest.mark.asyncio</code>. <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/812";>#812</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/fb5422f94d4a85b8f2a0ea2731f5ebeae5fcd7e8";><code>fb5422f</code></a> docs: Set release date for v0.24 in changelog.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/6dc7f584e71476c09393cca65c813c624ecc5882";><code>6dc7f58</code></a> docs: Add migration guides for pytest-asyncio v0.21 and v0.23.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/1bfc18164693026d897ebb48ed6e72d85d87fa44";><code>1bfc181</code></a> Wire Sphinx builds into the RTD config via tox</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/f03cf13b05f08b8a27f9f33ae578d1caec896d72";><code>f03cf13</code></a> Build(deps): Bump hypothesis in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/69540bfae3865ebb0395a549cf469fb07c04c08a";><code>69540bf</code></a> Build(deps): Bump attrs from 24.1.0 to 24.2.0 in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/b0ccfc5c5c196bec373fab247565e0158ff39582";><code>b0ccfc5</code></a> Build(deps): Bump hypothesis in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/574f1db6869146163cd21b65545494cf517712e2";><code>574f1db</code></a> Build(deps): Bump babel from 2.15.0 to 2.16.0 in /dependencies/docs</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/ae30dac2f7b9af62f3ef7ef614a5c99284a94271";><code>ae30dac</code></a> Update .readthedocs.yaml to install pytest-asyncio</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/972a7045adcaff98a151ec632a9205497afe373d";><code>972a704</code></a> Derive project version using importlib</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/d587a521a4aab33275c1352f7832e5e21c4bab93";><code>d587a52</code></a> [pre-commit.ci] pre-commit autoupdate</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-asyncio/compare/v0.23.8...v0.24.0";>compare view</a></li> </ul> </details> <br /> [](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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
