[dependabot]

Bumps pytest from 8.4.2 to 9.1.1.

Release notes

Sourced from pytest's releases.

9.1.1

pytest 9.1.1 (2026-06-19)

Bug fixes

• #14220: Fixed a logic bug in pytest.RaisesGroup which would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages.
• #14591: Fixed a regression in pytest 9.1.0 which caused overriding a parametrized fixture with an indirect @​pytest.mark.parametrize to fail with "duplicate parametrization of '<fixture name>'".
• #14606: Fixed list-item typing errors from mypy in @pytest.mark.parametrize <pytest.mark.parametrize ref> argvalues parameter.
• #14608: Fixed a regression in pytest 9.1.0 where conftest.py files located in <invocation dir>/test* were no longer loaded as initial conftests when invoked without arguments. This could cause certain hooks (like pytest_addoption) in these files to not fire.

9.1.0

pytest 9.1.0 (2026-06-13)

Removals and backward incompatible breaking changes

• #14533: When using --doctest-modules, autouse fixtures with module, package or session scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

  If this is undesirable, move the fixture definition to a conftest.py file if possible.

  Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as pytest.Module and once as a DoctestModule (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the DoctestModule collects a fixture, it is now visible to it only, and not to the Module. This means that both need to register the fixtures independently.

Deprecations (removal in next major release)

• #10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without @classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use @classmethod decorator instead -- by yastcher.

  See 10819 and 14011.

• #12882: Calling request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue> during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

  See dynamic-fixture-request-during-teardown for details.

• #13409: Using non-~collections.abc.Collection iterables (such as generators, iterators, or custom iterable objects) for the argvalues parameter in @pytest.mark.parametrize <pytest.mark.parametrize ref> and metafunc.parametrize <pytest.Metafunc.parametrize> is now deprecated.

  These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running pytest.main() multiple times, using class-level parametrize decorators, or collecting tests multiple times.

  See parametrize-iterators for details and suggestions.

• #13946: The private config.inicfg attribute is now deprecated. Use config.getini() <pytest.Config.getini> to access configuration values instead.

  See config-inicfg for more details.

• #14004: Passing baseid to ~pytest.FixtureDef or nodeid strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

... (truncated)

Commits

• cf470ec Prepare release version 9.1.1
• e0c8ce6 Merge pull request #14625 from pytest-dev/patchback/backports/9.1.x/a07c31a97...
• 1b82d16 Merge pull request #14624 from pytest-dev/patchback/backports/9.1.x/b375b79ec...
• 501c4bc Merge pull request #14596 from bluetech/doc-classmethod
• b61f588 Merge pull request #14622 from chrisburr/fix-14608-initial-conftest-test-subdir
• 9a567e0 [automated] Update plugin list (#14617) (#14618)
• ef8b299 Merge pull request #14620 from pytest-dev/patchback/backports/9.1.x/680f9f3ed...
• 66abd07 Merge pull request #14220 from bysiber/fix-stale-iexp-raisesgroup
• 79fbf93 Merge pull request #14612 from pytest-dev/patchback/backports/9.1.x/974ed48b6...
• 0d312eb Merge pull request #14611 from bluetech/parametrize-argvalues-typing
• Additional commits viewable in compare view

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 commands and options

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 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)

[claude]

🔴 Async tests may break after merge: the lock now pairs pytest 9.1.1 with pytest-asyncio 0.23.3, a January 2024 release built for pytest 7. That pytest-asyncio release declares pytest>=7.0.0,<8, and the 0.23 line is known to break under pytest 8+. The cap pytest-asyncio>=0.21.1,<1.2.0 (pyproject.toml:59) excludes every pytest-asyncio release that supports pytest 9, so the relock downgraded instead of failing. Fix: raise the cap to pytest-asyncio>=1.3.0,<2 (the first line declaring pytest 9 support), then relock so pytest and pytest-asyncio metadata agree.

Why this was flagged

The trigger is uv sync with the dev group in CI or locally, then pytest. uv.lock:1732 pins pytest 9.1.1 and uv.lock:1747 pins pytest-asyncio 0.23.3, whose Requires-Dist is pytest<8,>=7.0.0, so the locked pair breaks that package's own constraint. pytest-asyncio 1.1.x and 1.2.x require pytest<9, and pytest 9 support starts in 1.3.0. The <1.2.0 cap in pyproject.toml:59 rules out every compatible release, and the resolver fell back to an old release instead of reporting a conflict. About 81 pytest.mark.asyncio uses (tests/unit/test_batch_evaluation.py, tests/unit/test_observe.py, tests/unit/test_openai.py, tests/unit/test_propagate_attributes.py, and others) depend on this plugin. On the base branch the pair is pytest 8.4.2 with pytest-asyncio 1.1.1, which works. After the merge, those async tests can error at collection or run, and uv lock --check may disagree with the committed lock.

Verification: The diff changes uv.lock from pytest 8.4.2 to version = "9.1.1" (uv.lock ~1732) and pytest-asyncio from 1.1.1 to version = "0.23.3" (uv.lock ~1747). The dev specifier stays pytest-asyncio>=0.21.1,<1.2.0 (pyproject.toml:59). This is a regression: the base lock (pytest 8.4.2 + pytest-asyncio 1.1.1) is a compatible pair.