dependabot[bot] opened a new pull request, #355: URL: https://github.com/apache/hudi-rs/pull/355
Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.3.5 to 8.4.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest/releases";>pytest's releases</a>.</em></p> <blockquote> <h2>8.4.1</h2> <h1>pytest 8.4.1 (2025-06-17)</h1> <h2>Bug fixes</h2> <ul> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/13461";>#13461</a>: Corrected <code>_pytest.terminal.TerminalReporter.isatty</code> to support being called as a method. Before it was just a boolean which could break correct code when using <code>-o log_cli=true</code>).</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/13477";>#13477</a>: Reintroduced <code>pytest.PytestReturnNotNoneWarning</code>{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.</p> <p>This warning is raised when a test functions returns a value other than <code>None</code>, which is often a mistake made by beginners.</p> <p>See <code>return-not-none</code>{.interpreted-text role="ref"} for more information.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/13497";>#13497</a>: Fixed compatibility with <code>Twisted 25+</code>.</p> </li> </ul> <h2>Improved documentation</h2> <ul> <li><a href="https://redirect.github.com/pytest-dev/pytest/issues/13492";>#13492</a>: Fixed outdated warning about <code>faulthandler</code> not working on Windows.</li> </ul> <h2>8.4.0</h2> <h1>pytest 8.4.0 (2025-06-02)</h1> <h2>Removals and backward incompatible breaking changes</h2> <ul> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/11372";>#11372</a>: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12346";>#12346</a>: Tests will now fail, instead of raising a warning, if they return any value other than None.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12874";>#12874</a>: We dropped support for Python 3.8 following its end of life (2024-10-07).</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12960";>#12960</a>: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.</p> <p>See <code>the docs <yield tests deprecated></code>{.interpreted-text role="ref"} for more information.</p> </li> </ul> <h2>Deprecations (removal in next major release)</h2> <ul> <li><a href="https://redirect.github.com/pytest-dev/pytest/issues/10839";>#10839</a>: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or <code>autouse=True</code>. For guidance on how to work around this warning see <code>sync-test-async-fixture</code>{.interpreted-text role="ref"}.</li> </ul> <h2>New features</h2> <ul> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/11538";>#11538</a>: Added <code>pytest.RaisesGroup</code>{.interpreted-text role="class"} as an equivalent to <code>pytest.raises</code>{.interpreted-text role="func"} for expecting <code>ExceptionGroup</code>{.interpreted-text role="exc"}. Also adds <code>pytest.RaisesExc</code>{.interpreted-text role="class"} which is now the logic behind <code>pytest.raises</code>{.interpreted-text role="func"} and used as parameter to <code>pytest.RaisesGroup</code>{.interpreted-text role="class"}. <code>RaisesGroup</code> includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating <code>except* <except_star></code>{.interpreted-text role="ref"}. See <code>assert-matching-exception-groups</code>{.interpreted-text role="ref"} and docstrings for more information.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12081";>#12081</a>: Added <code>capteesys</code>{.interpreted-text role="fixture"} to capture AND pass output to next handler set by <code>--capture=</code>.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12504";>#12504</a>: <code>pytest.mark.xfail</code>{.interpreted-text role="func"} now accepts <code>pytest.RaisesGroup</code>{.interpreted-text role="class"} for the <code>raises</code> parameter when you expect an exception group. You can also pass a <code>pytest.RaisesExc</code>{.interpreted-text role="class"} if you e.g. want to make use of the <code>check</code> parameter.</p> </li> <li> <p><a href="https://redirect.github.com/pytest-dev/pytest/issues/12713";>#12713</a>: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest/commit/8d99211f0ce3927eb7ee579f7b4f969da06dc787";><code>8d99211</code></a> Prepare release version 8.4.1</li> <li><a href="https://github.com/pytest-dev/pytest/commit/5dc5880715633c97310c0593f0ae356de27fa933";><code>5dc5880</code></a> docs: update pytest.ini addopts example to use separate -p entries (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13529";>#13529</a>) (...</li> <li><a href="https://github.com/pytest-dev/pytest/commit/d0c7ed0bfae5a5f1f9153cd1e464a421d701e925";><code>d0c7ed0</code></a> Reintroduce PytestReturnNotNoneWarning (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13495";>#13495</a>) (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13527";>#13527</a>)</li> <li><a href="https://github.com/pytest-dev/pytest/commit/a1b3a7879589eb437e4fd97c169b228c3ed58c63";><code>a1b3a78</code></a> Fix compatibility with Twisted 25 (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13502";>#13502</a>) (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13531";>#13531</a>)</li> <li><a href="https://github.com/pytest-dev/pytest/commit/4c161aba8ecaab9940040702369025595d26564c";><code>4c161ab</code></a> pytester: avoid unraisableexception gc collects in inline runs to speed up te...</li> <li><a href="https://github.com/pytest-dev/pytest/commit/a86ee09291f913b36fdeec14c42356515b91c979";><code>a86ee09</code></a> Fix typo in parametrize.rst (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13514";>#13514</a>) (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13516";>#13516</a>)</li> <li><a href="https://github.com/pytest-dev/pytest/commit/1a0581b0227fa07afd1f2c4c6215aec3862cf1ab";><code>1a0581b</code></a> Remove outdated warning about faulthandler_timeout on Windows (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13492";>#13492</a>) (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13493";>#13493</a>)</li> <li><a href="https://github.com/pytest-dev/pytest/commit/4e631a71484c2fa49e3fd9f884546af411a4888d";><code>4e631a7</code></a> Merge pull request <a href="https://redirect.github.com/pytest-dev/pytest/issues/13486";>#13486</a> from hosmir/fixtypo (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13487";>#13487</a>)</li> <li><a href="https://github.com/pytest-dev/pytest/commit/b49745ec529f06edfbbe531b766839763b2be3c2";><code>b49745e</code></a> fix: support TerminalReporter.isatty being called (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13462";>#13462</a>) (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13483";>#13483</a>)</li> <li><a href="https://github.com/pytest-dev/pytest/commit/cc5ceed916d0c63696da33c67e035917194a4e87";><code>cc5ceed</code></a> RELEASING: remove pytest mailing list (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13472";>#13472</a>) (<a href="https://redirect.github.com/pytest-dev/pytest/issues/13473";>#13473</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest/compare/8.3.5...8.4.1";>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]
