cjrh / misu

94%

LAST BUILD ON BRANCH master

branch: SELECT

CHANGE BRANCH

x

• No branch selected
• chore-update-pyo3-0-29
• dependabot/add-v2-config-file
• dependabot/pip/pytest-6.0.2
• dependabot/pip/pytest-6.1.0
• dependabot/pip/pytest-6.1.1
• dependabot/pip/pytest-6.1.2
• dependabot/pip/pytest-6.2.1
• dependabot/pip/pytest-6.2.2
• dependabot/pip/pytest-6.2.3
• dependabot/pip/pytest-6.2.4
• dependabot/pip/pytest-9.1.1
• dependabot/pip/pytest-9.2.0
• improved-benchmark-and-doc
• last-commit
• master
• new-version-1.0.6
• rewrite-in-rust
• setup-trusted-publishing-pypi
• tag-push-with-cargo-release
• threads-gil-freethreaded
• update-versions
• v1.0.4
• v1.0.5
• v1.0.6

Build # 41632852426

Build Type

push

github

Committed by web-flow

Commit Message

Bump pytest from 9.1.1 to 9.2.0 (#65)

Bumps [pytest](https://github.com/pytest-dev/pytest) from 9.1.1 to
9.2.0.
<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>9.2.0</h2>
<h1>pytest 9.2.0 (2026-10-27)</h1>
<h2>Removals and backward incompatible breaking changes</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/14716">#14716</a>:
<code>-c</code> now raises a usage error for a path that does not exist,
is a directory, or is in a format pytest has no loader for. Such paths
were previously either ignored or reported as an unhandled
<code>FileNotFoundError</code>.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/8593">#8593</a>:
The <code>indirect</code>, <code>ids</code> and <code>scope</code>
arguments of <code>Metafunc.parametrize()
&lt;pytest.Metafunc.parametrize&gt;</code> -- and therefore of
<code>@pytest.mark.parametrize &lt;pytest.mark.parametrize
ref&gt;</code> -- are now keyword-only.</p>
<p>Passing them positionally was a common source of confusing errors,
e.g. <code>parametrize(&quot;arg1&quot;, &quot;arg2&quot;, [(1,
2)])</code> made the argvalues land in <code>indirect</code> and failed
with <code>indirect fixture '(1, 2)' doesn't exist</code>; such mistakes
now fail with an understandable <code>TypeError</code>. The type
annotations have always declared these arguments as keyword-only.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/993">#993</a>:
Plugin import failures at startup are now reported and classified
instead of escaping as a raw traceback with the accidental exit code
<code>1</code>:</p>
<ul>
<li>a plugin that cannot be found -- via <code>-p</code>,
<code>pytest_plugins</code> or <code>PYTEST_PLUGINS</code> -- exits with
<code>pytest.ExitCode</code> <code>USAGE_ERROR</code> (<code>4</code>),
like a <code>conftest.py</co... (continued)

Coverage Stats

1063 of 1127 relevant lines covered (94.32%)

124.44 hits per line