Commit 3401969
authored
![frequenz-auto-dependabot[bot]](https://avatars.githubusercontent.com/in/2857719?v=4&size=40){kind=avatar}
chore(deps-dev): Bump the minor group across 1 directory with 2 updates (#112)
Bumps the minor group with 2 updates in the / directory:
[pytest](https://github.com/pytest-dev/pytest) and
[setuptools-scm](https://github.com/pypa/setuptools-scm).
Updates `pytest` from 9.0.3 to 9.1.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>9.1.1</h2>
<h1>pytest 9.1.1 (2026-06-19)</h1>
<h2>Bug fixes</h2>
<ul>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/14220">#14220</a>:
Fixed a logic bug in <code>pytest.RaisesGroup</code> which would might
cause it to display incorrect "It matches <!-- raw HTML omitted
-->FooError()<!-- raw HTML omitted --> which was paired with <!-- raw
HTML omitted -->BarError<!-- raw HTML omitted -->" messages.</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/14591">#14591</a>:
Fixed a regression in pytest 9.1.0 which caused overriding a
parametrized fixture with an indirect <!-- raw HTML omitted --><a
href="https://github.com/pytest"><code>@pytest</code></a>.mark.parametrize<!--
raw HTML omitted --> to fail with "duplicate parametrization of
'<fixture name>'".</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/14606">#14606</a>:
Fixed <code>list-item</code> typing errors from mypy in
<code>@pytest.mark.parametrize <pytest.mark.parametrize
ref></code> <code>argvalues</code> parameter.</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/14608">#14608</a>:
Fixed a regression in pytest 9.1.0 where <code>conftest.py</code> files
located in <code><invocation dir>/test*</code> were no longer
loaded as initial conftests when invoked without arguments.
This could cause certain hooks (like <code>pytest_addoption</code>) in
these files to not fire.</li>
</ul>
<h2>9.1.0</h2>
<h1>pytest 9.1.0 (2026-06-13)</h1>
<h2>Removals and backward incompatible breaking changes</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/14533">#14533</a>:
When using <code>--doctest-modules</code>, autouse fixtures with
<code>module</code>, <code>package</code> or <code>session</code> scope
that are defined inline in Python test modules (not plugins or
conftests) will now possibly execute twice.</p>
<p>If this is undesirable, move the fixture definition to a
<code>conftest.py</code> file if possible.</p>
<p>Technical explanation for those interested:
When using <!-- raw HTML omitted -->--doctest-modules<!-- raw HTML
omitted -->, pytest possibly collects Python modules twice, once as
<code>pytest.Module</code> and once as a <code>DoctestModule</code>
(depending on the configuration).
Due to improvements in pytest's fixture implementation, if e.g. the
<code>DoctestModule</code> collects a fixture, it is now visible to it
only, and not to the <code>Module</code>.
This means that both need to register the fixtures independently.</p>
</li>
</ul>
<h2>Deprecations (removal in next major release)</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10819">#10819</a>:
Added a deprecation warning for class-scoped fixtures defined as
instance methods (without <code>@classmethod</code>). Such fixtures set
attributes on a different instance than the test methods use, leading to
unexpected behavior. Use <code>@classmethod</code> decorator instead --
by <code>yastcher</code>.</p>
<p>See <code>10819</code> and <code>14011</code>.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12882">#12882</a>:
Calling <code>request.getfixturevalue()
<pytest.FixtureRequest.getfixturevalue></code> during teardown to
request a fixture that was not already requested is now deprecated and
will become an error in pytest 10.</p>
<p>See <code>dynamic-fixture-request-during-teardown</code> for
details.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/13409">#13409</a>:
Using non-<code>~collections.abc.Collection</code> iterables (such as
generators, iterators, or custom iterable objects) for the
<code>argvalues</code> parameter in <code>@pytest.mark.parametrize
<pytest.mark.parametrize ref></code> and
<code>metafunc.parametrize <pytest.Metafunc.parametrize></code> is
now deprecated.</p>
<p>These iterables get exhausted after the first iteration,
leading to tests getting unexpectedly skipped in cases such as running
<code>pytest.main()</code> multiple times,
using class-level parametrize decorators,
or collecting tests multiple times.</p>
<p>See <code>parametrize-iterators</code> for details and
suggestions.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/13946">#13946</a>:
The private <code>config.inicfg</code> attribute is now deprecated.
Use <code>config.getini() <pytest.Config.getini></code> to access
configuration values instead.</p>
<p>See <code>config-inicfg</code> for more details.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/14004">#14004</a>:
Passing <code>baseid</code> to <code>~pytest.FixtureDef</code> or
<code>nodeid</code> strings to fixture registration APIs is now
deprecated. These are internal pytest APIs that are used by some
plugins.</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/cf470ec0bf7eb89cd97dd56df4859eae5db46447"><code>cf470ec</code></a>
Prepare release version 9.1.1</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/e0c8ce6cc5db1f08363be6f152c32e6838df2690"><code>e0c8ce6</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14625">#14625</a>
from pytest-dev/patchback/backports/9.1.x/a07c31a97...</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/1b82d1694fce22385ee7a4287917fbafbaf2e757"><code>1b82d16</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14624">#14624</a>
from pytest-dev/patchback/backports/9.1.x/b375b79ec...</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/501c4bc784da3b08bfcaa64858eba5d15dc59e53"><code>501c4bc</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14596">#14596</a>
from bluetech/doc-classmethod</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/b61f588e36e9377c3d1d3f06bece1da0fc31d9ca"><code>b61f588</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14622">#14622</a>
from chrisburr/fix-14608-initial-conftest-test-subdir</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/9a567e009f4d2da3ce1721c6db3109cb5744d40a"><code>9a567e0</code></a>
[automated] Update plugin list (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/14617">#14617</a>)
(<a
href="https://redirect.github.com/pytest-dev/pytest/issues/14618">#14618</a>)</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/ef8b2993e5b48639e4a3d97d0525df9760781384"><code>ef8b299</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14620">#14620</a>
from pytest-dev/patchback/backports/9.1.x/680f9f3ed...</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/66abd0784d4cb7c1ba44ab9a8896506cd4985acc"><code>66abd07</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14220">#14220</a>
from bysiber/fix-stale-iexp-raisesgroup</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/79fbf93b666cac5f27c9dad047943d47b766c8d5"><code>79fbf93</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14612">#14612</a>
from pytest-dev/patchback/backports/9.1.x/974ed48b6...</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/0d312eb876177e9f1c04262b54060a41034ebf5c"><code>0d312eb</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/14611">#14611</a>
from bluetech/parametrize-argvalues-typing</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest/compare/9.0.3...9.1.1">compare
view</a></li>
</ul>
</details>
<br />
Updates `setuptools-scm` from 10.0.5 to 10.2.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pypa/setuptools-scm/releases">setuptools-scm's
releases</a>.</em></p>
<blockquote>
<h2>setuptools-scm v10.2.0</h2>
<h3>Added</h3>
<ul>
<li>Restore Python 3.8 and 3.9 support, re-enabling use as a build
dependency for projects like scikit-build that still support these
versions. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1445">#1445</a>)</li>
</ul>
<h3>Miscellaneous</h3>
<ul>
<li>Move PKG-INFO discovery tests from vcs-versioning to setuptools-scm
where the entry points are registered. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1446">#1446</a>)</li>
</ul>
<h2>setuptools-scm v10.1.2</h2>
<h3>Fixed</h3>
<ul>
<li>Fix DeprecationWarning leak by threading VcsEnvironment through
VersionInferenceConfig and using env.make_reader() in
_should_write_to_source. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1424">#1424</a>)</li>
</ul>
<h2>setuptools-scm v10.1.1</h2>
<h3>Fixed</h3>
<ul>
<li>Update CI to use PyPy 3.11 as cryptography has no PyPy 3.10 build
available (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1421">#1421</a>)</li>
</ul>
<h2>setuptools-scm v10.1.0</h2>
<h3>Added</h3>
<ul>
<li>Add backward-compatible shims in <code>setuptools_scm.git</code>,
<code>setuptools_scm.hg</code>, <code>setuptools_scm.hg_git</code>, and
<code>setuptools_scm.scm_workdir</code> so that external code calling
<code>get_scm_version(config)</code> or
<code>run_describe(config)</code> with an explicit
<code>Configuration</code> continues to work. The shim automatically
wires <code>_config</code> and <code>VcsEnvironment</code> onto the
workdir. (<a
href="https://github.com/pypa/setuptools-scm/issues/compat-shims">#compat-shims</a>)</li>
<li>Write <code>scm_version.json</code> and
<code>scm_file_list.json</code> into egg-info directories during
<code>egg_info</code>, enabling sdist fallback version inference when no
VCS is present. Add <code>ScmEggInfoMixin</code> for workdir-based file
finding in <code>find_sources()</code>. (<a
href="https://github.com/pypa/setuptools-scm/issues/egg-info-metadata">#egg-info-metadata</a>)</li>
<li>Add <code>write_to_source</code> pyproject.toml option to control
whether version files are written to the source tree. When unset, a
deprecation warning advises setting it explicitly before the default
changes in a future major release. The
<code>SETUPTOOLS_SCM_WRITE_TO_SOURCE</code> environment variable
overrides this setting. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1301">#1301</a>)</li>
<li>Adopt the workdir-centric pipeline from vcs-versioning: version
discovery now follows an explicit <code>env → config → workdir →
version</code> chain instead of relying on ambient globals and
<code>parse</code> entry points. The <code>egg_info</code> command
writes <code>scm_version.json</code> and <code>scm_file_list.json</code>
metadata so sdists can infer versions without a VCS checkout. Requires
<code>vcs-versioning >= 2.0.0.dev0</code>. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1378">#1378</a>)</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Fix worktree file listing test to expect relative paths from the
file finder. The test now passes on Linux; Windows remains xfail due to
a subprocess limitation with worktree directories. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/620">#620</a>)</li>
<li>Remove the <code>_warn_on_old_setuptools()</code> check that
incorrectly warned when a custom build-backend caused
<code>setuptools.__version__</code> to return the project version
instead of setuptools' version. The minimum setuptools version is now
enforced via build-system requirements. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1192">#1192</a>)</li>
<li>Wrap version in <code>setuptools.sic()</code> when <code>normalize =
false</code> to prevent setuptools from re-normalizing the version after
our hook returns. This preserves CalVer zero-padding (e.g.
<code>2024.01.05</code>) and other non-canonical version strings in
<code>dist.metadata.version</code>. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1354">#1354</a>)</li>
<li>Skip writing non-package version files to build_lib, fixing
incorrect inclusion of root-level version files in wheels. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1364">#1364</a>)</li>
</ul>
<h3>Documentation</h3>
<ul>
<li>Rewrite the GitHub Actions CI/CD example to use a dedicated build
job
(via <code>build-and-inspect-python-package</code>) and OIDC Trusted
Publishers
instead of building in publishing jobs with long-lived API tokens. (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1215">#1215</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/a70589150e28f43aded5852eed09765f69bfff66"><code>a705891</code></a>
Merge pull request <a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1448">#1448</a>
from pypa/release/main</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/630448e286a636eb378b449541b1c96819cb9d05"><code>630448e</code></a>
Prepare release: setuptools-scm v10.2.0, vcs-versioning v2.2.0</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/aaf4950434a9b06c99e5fcdbd720f5abbd04345d"><code>aaf4950</code></a>
Merge pull request <a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1445">#1445</a>
from RonnyPfannschmidt/python-legacy</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/dd60bf93ed795243e5b1d60b093dae76e390d00b"><code>dd60bf9</code></a>
Merge pull request <a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1447">#1447</a>
from RonnyPfannschmidt/fix/1446-move-pkginfo-tests</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/535f5ff5f505635a4401f91f46f4b152e6a062f2"><code>535f5ff</code></a>
fix: move PKG-INFO discovery tests to setuptools-scm (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1446">#1446</a>)</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/3546a0e2c02dd093601cce206b1a4cf42f783fd0"><code>3546a0e</code></a>
feat: restore Python 3.8 and 3.9 support</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/0cde12385f2bc90c90287c8ca2e2e8f7e423fd45"><code>0cde123</code></a>
Merge pull request <a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1443">#1443</a>
from pypa/release/main</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/51bc391cec1f651a7038a6e8e19ba317f92ee75e"><code>51bc391</code></a>
Prepare release: vcs-versioning v2.1.2</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/310f3c35e978132d8b61d3c808fcdd9ab08a7d72"><code>310f3c3</code></a>
Merge pull request <a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1442">#1442</a>
from RonnyPfannschmidt/fix/1439-metadata-workdir-cus...</li>
<li><a
href="https://github.com/pypa/setuptools-scm/commit/b7b70a8769dfa70df77ada852b5030e626a7faab"><code>b7b70a8</code></a>
fix: don't re-parse stored tags through tag_regex in MetadataWorkdir (<a
href="https://redirect.github.com/pypa/setuptools-scm/issues/1439">#1439</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/pypa/setuptools-scm/compare/setuptools-scm-v10.0.5...setuptools-scm-v10.2.0">compare
view</a></li>
</ul>
</details>
<br />1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
| 7 | + | |
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
| |||
97 | 97 | | |
98 | 98 | | |
99 | 99 | | |
100 | | - | |
| 100 | + | |
101 | 101 | | |
102 | 102 | | |
103 | 103 | | |
| |||
0 commit comments