Bump the minor_and_patch group with 3 updates

[dependabot]

Bumps the minor_and_patch group with 3 updates: pylint, pytest and pytest-describe.

Updates pylint from 4.0.5 to 4.0.6

Commits

• 8a39635 Bump pylint to 4.0.6, update changelog (#11105)
• 150f23c [Backport maintenance/4.0.x] Allow digits in ParamSpec and TypeVarTuple names...
• 8b6251e [Backport maintenance/4.0.x] Fix crash when enum member inference fails (#11093)
• d57aadb [Backport maintenance/4.0.x] Fix implicit-str-concat false positive for mix...
• d9ea8d9 [Backport maintenance/4.0.x] Fix unnecessary-comprehension suggestion when ...
• cb1792a [Backport maintenance/4.0.x] Allow digits in TypeVar names for invalid-name c...
• ee2ab9a Handle InferenceError in decorator return analysis
• 5bb5498 [Backport maintenance/4.0.x] Fix crash in typecheck checker when metaclass ar...
• a940533 [Backport maintenance/4.0.x] Fix a crash in consider-using-enumerate for no...
• b7a873a [Backport maintenance/4.0.x] Fix crash in deprecated checker for non-string `...
• Additional commits viewable in compare view

Updates pytest from 9.0.3 to 9.1.0

Release notes

Sourced from pytest's releases.

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.

  Use the node parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used nodeid=None, pass node=session instead.

  This will be removed in pytest 10.

• #14335: The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See hook-markers for more details.

• #14434: The --pastebin option is now deprecated.

... (truncated)

Commits

• b2522cf Prepare release version 9.1.0
• 368d2fc [refactor] Tighten SetComparisonFunction to Iterator[str] (#14587)
• ff77cd8 [refactor] Make base assertion comparisons return an iterator instead of a li...
• 0d8491a build(deps): Bump actions/stale from 10.2.0 to 10.3.0
• 4a809d9 Merge pull request #14568 from pytest-dev/register-fixture
• 5dfa385 Fix recursion traceback test to cover all styles (#14582)
• f52ff0c Add pytest.register_fixture
• a8ac094 Merge pull request #14567 from pytest-dev/more-visibility-deprecate
• e5620cd [pre-commit.ci] pre-commit autoupdate (#14577)
• 2ce9c6d Merge pull request #14540 from minbang930/fix-14533-doctest-module-fixtures
• Additional commits viewable in compare view

Updates pytest-describe from 3.1.0 to 3.2.0

Release notes

Sourced from pytest-describe's releases.

3.2.0

Version 3.2.0 of the pytest-describe plugin

This version supports pytest 7.0 to 9.0 on Python 3.10 to 3.14.

New features:

• Fixtures as describe block arguments (#54): When several tests in a describe-block need the same fixture, you can now pass the fixture name as an argument to the describe function instead of repeating it in every test. See the README for details and caveats.

• Docstrings as describe block names (#41, #55): With the new opt-in describe_docstrings configuration option, describe-blocks are reported under the first line of their docstring instead of their function name, allowing for more descriptive test reports like test_wallet.py::a wallet::when it is empty::it_has_no_balance. See the README for how to enable it.

• Access to describe functions for plugins (#53, #55): The new public function get_describe_functions returns the describe functions wrapping a collected test item, so that reporting plugins can show describe block names or docstrings in their output. See the README for a usage example.

• The package now ships with complete type hints, verified with mypy in strict mode.

Breaking changes:

• Support for Python 3.9 and pytest 6 has been dropped.

Thanks to everyone who contributed to this release with ideas and feedback!

Commits

• bcb7119 Improve README a bit
• 23aed77 Expose describe functions and use docstrings as block names (#55)
• 0b8ea18 Support fixtures as describe block arguments (#54)
• 40238f7 Improve trigger condition for publishing
• 3379f48 Add type hints and check them with mypy
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions