[renovate-ce-it-martin-bens]

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
click (changelog)	8.4.1 → 8.5.0
mypy (changelog)	2.1.0 → 2.4.1
pre-commit	4.6.0 → 4.7.0
pytest (changelog)	9.0.3 → 9.2.0
ruff (source, changelog)	0.15.14 → 0.17.3
typer (changelog)	0.25.1 → 0.27.3
typos (changelog)	1.46.3 → 1.51.1

---

Release Notes

pallets/click (click)

v8.5.0

Compare Source

Released 2026-08-24

• Add built-in shell completion support for PowerShell (Windows PowerShell
  5.1+ and pwsh 7+) alongside the existing bash, zsh, and fish
  completers. Use _FOO_BAR_COMPLETE=powershell_source foo-bar to generate
  the completion script. {issue}2672 {pr}3637
• Supported versions of Windows enable ANSI terminal styles by default.
  Colorama is no longer a dependency and is not used. {issue}2986 {pr}3505
• {class}Argument accepts a help parameter, and help output includes
  a Positional arguments section when argument help is available. {issue}2983 {pr}3473
• confirm() and prompt() strip ANSI color and style codes from the
  prompt when the output stream does not support them, matching echo().
  This stripping was lost in 8.4.0 when {pr}2969 began writing the
  prompt with input() directly. {issue}3572 {pr}3653
• Fix test failures when using pytest >= 9.1. {pr}3656
• {class}Path with allow_dash=True no longer triggers a BytesWarning,
  an error under python -bb, when checking a value against the -
  convention. {issue}2877 {pr}3642
• Add {func}custom_version_option, a --version option whose output is
  produced by a callback, covering cases {func}version_option intentionally
  does not. The feature set of {func}version_option is now frozen; see
  discussion #​3527. {pr}3581
• style() and secho() no longer silently drop the 256-color index 0
  (black) passed as fg or bg, and now validate color arguments. Invalid
  colors raise a ValueError instead of a TypeError. {pr}3677
• The automatic help option stores its value under the reserved name
  _click_default_help instead of help, so a parameter named help no
  longer breaks parsing. The new name is visible in
  {meth}Command.to_info_dict output. Parameters that overwrite each other's
  value trigger a warning: an argument sharing its name with another
  parameter, or any parameter claiming the reserved name. Options may still
  share a name to compete for the same value (feature switches).
  {issue}2819 {pr}3678
• unstyle and the ANSI handling behind help-text wrapping now strip the full
  CSI escape-sequence grammar. {pr}3681
• Streamline Option flag handling: the flag-kind, type, lazy-default and
  validation steps in Option.__init__ move into focused helpers, and
  flag_value and default keep their unset sentinel at construction
  (resolved lazily on read) so is UNSET reliably tells a user-supplied value
  from an auto-derived one. Runtime behavior is unchanged, but
  {meth}Parameter.to_info_dict now resolves default=True on a feature
  switch to its flag_value, matching what the function receives at call
  time. {pr}3641
• {func}get_binary_stream and {func}get_text_stream are deprecated and
  will be removed in Click 9.0. {issue}3481 {pr}3695
• The following click.utils names were never intentionally public and are
  now private (_-prefixed). The old names remain available with a
  DeprecationWarning until Click 9.0: LazyFile, KeepOpenFile,
  make_default_short_help, PacifyFlushWrapper, and safecall.
  {issue}3099 {pr}3695
• Deprecate {meth}CliRunner.isolated_filesystem. It relies on
  {func}os.chdir, which mutates process-global state and is not
  thread-safe. The helper predates Python 3 and modern pytest: use a
  temporary directory ({class}tempfile.TemporaryDirectory or pytest's
  tmp_path fixture) with absolute paths instead. For running tests in
  parallel, use process-based isolation (such as pytest-xdist) rather
  than threads, since {meth}CliRunner.invoke also redirects the
  process-global standard streams. {issue}3501 {issue}3700 {pr}3704
• prompt() is now generically typed and returns the type produced by
  type, value_proc, or a matching default instead of Any.
  {class}ParamType takes a second optional type parameter describing the
  input value it accepts (ParamType[int, str] for a type converting
  strings to integers), defaulting to Any. {pr}3407
• {meth}Command.get_help_option_names returns the help option names in the
  order they were declared. {pr}3728
• {func}get_pager_file yields a text stream on Windows again. The temporary
  file backend opened its file in binary mode, so writing a str to the pager
  raised TypeError: a bytes-like object is required, not 'str', and the
  color argument was ignored on that path. Regression introduced in 8.4.0
  by {pr}1572. {issue}3731 {issue}3732 {issue}3740 {pr}3739
• {func}progressbar settles on its final position when update_min_steps
  does not divide the total. Steps below that threshold are applied when the
  bar finishes, so show_pos renders 20/20 rather than the last multiple
  it reached. {issue}3571 {pr}3769
• An error raised while writing to the pager no longer gets replaced by
  PermissionError: [WinError 32] on Windows. The temporary file backend
  unlinked its file without closing it first, and Windows refuses to remove a
  file the process still holds open, so the cleanup failure masked the real
  exception. {issue}3731 {pr}3764
• The temporary file the pager writes to on Windows is opened with the encoding
  {func}get_pager_file picked for the output stream, and with
  errors="replace" to match the pipe backend. Any text stdout can encode
  reaches the pager.
• The temporary file pager backend forwards any parameters the user set in
  PAGER to the pager command instead of silently dropping them. On Windows,
  PAGER="less -R" now invokes less -R on the temporary file rather than
  bare less. {pr}3777
• Improve raw mode detection by parsing the option tokens. {issue}3416
  {pr}3777
• {func}edit accepts os.PathLike values for filename, in addition to
  strings. {issue}2869 {pr}3781

v8.4.2

Compare Source

Released 2026-06-24

• Fix Fish shell completion broken in 8.4.0 by {pr}3126. Newlines and
  tabs in option help text are now escaped, keeping the original completion
  format while still supporting multi-line help. {issue}3502
  {issue}3043 {pr}3504 {pr}3508
• Deprecated commands and options with empty or missing help text no longer
  render a stray leading space before the (DEPRECATED) label. {pr}3509
• A {class}Group with invoke_without_command=True marks its subcommand as
  optional in the usage help, showing [COMMAND] instead of COMMAND.
  {issue}3059 {pr}3507
• echo_via_pager flushes after each write, so passing a generator streams
  output to the pager incrementally instead of staying hidden until the pipe
  buffer fills. {issue}3242 {issue}2542 {pr}3534
• echo_via_pager and get_pager_file no longer close a borrowed stdout
  stream when no external pager runs, completing the partial
  I/O operation on closed file fix from {pr}3482. {issue}3449
  {pr}3533
• Fix CLI usage symopsis for optional arguments producing double square brackets
  [[a|b|c]]... whose type already brackets their metavar. {pr}3578
• {func}version_option resolves a package_name that does not match an
  installed distribution as an import (top-level module) name via
  {func}importlib.metadata.packages_distributions. Packages whose
  top-level module name differs from their distribution name (PIL vs
  Pillow, jwt vs PyJWT) no longer raise RuntimeError out of the
  box. {issue}2331 {issue}1884 {issue}3125 {pr}3582

python/mypy (mypy)

v2.4.1

Compare Source

• Process overloads as a whole in two-phase type checking (Ivan Levkivskyi, PR 22231)
• Skip recursive setup for frame-private nested functions in mypyc (Piotr Sawicki, PR 22187)

v2.4.0

Compare Source

v2.3.1

Compare Source

• Fix mypyc crash on double yielding Iterators (Daniël van Noord, PR 21826)
• Fix mypyc default_factory for inherited dataclass (Daniël van Noord, PR 21785)
• Clear mypyc coroutine env on coroutine completion (Piotr Sawicki, PR 21734)
• Fix crash when unpacking return value from overload (Shantanu, PR 21830)

v2.3.0

Compare Source

v2.2.0

Compare Source

pre-commit/pre-commit (pre-commit)

v4.7.0

Compare Source

==================

Fixes

• Fix language: node hooks during commit with -a or inside a submodule.
  • Regressed in 4.6.1.
  • #​3773 issue by @​cbirkhold.
  • #​3774 PR by @​cbirkhold.

v4.6.2

Compare Source

==================

Fixes

• Fix language: node hooks that contain "scripts": {"build": ...} with
  npm 11.x.
  • Regressed in 4.6.1.
  • #​3737 issue by @​mheiges.
  • #​3743 PR by @​asottile.

v4.6.1

Compare Source

==================

Fixes

• Install language: node hooks via git.
  • Fixes npm 12.x compatibility
  • #​3719 PR by @​asottile.
  • #​3517 issue by @​ojob.
• Set JULIA_DEPOT_PATH for language: julia.
  • #​3711 PR by @​damonbayer.
  • pre-commit-ci/runner-image#335 issue by @​damonbayer.
• Produce error on mistyped --repo for pre-commit autoupdate.
  • #​3701 PR by @​mxr.
  • #​3695 issue by @​mxr.
• Improve performance of commit existence check in pre-push.
  • #​3726 PR by @​asottile.
  • #​3604 issue by @​ptarjan.
• Avoid duplicating conflicted filenames during pre-commit run --all-files.
  • #​3727 PR by @​asottile.
  • #​3706 issue by @​RomanValov.

pytest-dev/pytest (pytest)

v9.2.0

Compare Source

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

• #​14716: -c 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 FileNotFoundError.

• #​8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

  Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

• #​993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:

  • a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
  • a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.

  pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

• #​14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec.
  The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.

• #​14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.

• #​14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1,
  all higher-scoped fixtures (module, package, and session) defined
  as instance methods are now deprecated.

  They suffer from the same issue the original deprecation only fixed for
  class-scoped fixtures, see 10819 and 14011.

• #​14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.

• #​7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

• #​14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
• #​2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
• #​6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

• #​10745: A RecursionError whose recursion origin cannot be located now shows only the
  first and last 10 stack frames, matching what pytest already did when locating
  the origin failed outright. Previously the full traceback -- often around a
  thousand near-identical frames -- was rendered, which was both slow and
  unreadable. Pass --full-trace to see every frame.

• #​10745: The line numbers of a module's statements are now computed once per traceback
  instead of once per traceback entry, which noticeably speeds up rendering
  failures raised from large test modules.

• #​11418: The cached rewritten modules in __pycache__ are now invalidated by a hash of
  the source instead of its modification time, using the checked-hash pyc format
  from 552.

  Timestamps make the cache useless wherever source files get fresh modification
  times, most notably in CI: a checkout gives every file a new mtime, so a
  restored cache is discarded in full and every test module is rewritten again.
  Hashing the source costs roughly 15 microseconds per file and makes the cache
  survive that.

  Existing timestamp based caches are ignored and rewritten once.

• #​12624: The pytest_plugins variable and the PYTEST_PLUGINS environment variable now also accept entry point names of installed plugins (e.g. xdist), in addition to importable module names, matching the behavior of the -p command-line option.

  As part of this change, plugins specified by entry point name through these mechanisms are now also listed in the plugins: line of the terminal header (12615).

  Based on the original implementation by Marcel Telka in 12616.

• #​12697: Warnings emitted while importing plugins through -p, PYTEST_PLUGINS, or entry point autoloading are now captured, filtered, and reported like other warnings.

• #​12860: Assertion diffs for dict.items() and dict.keys() comparisons (>=, <=, >, <, ==) now show which items are missing, the same way set comparisons do.

• #​13354: Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> now also accepts a ~pytest.MarkDecorator as its default, for example item.get_closest_marker("foo", pytest.mark.foo(1)), and returns the wrapped ~pytest.Mark.

  Previously the only way to build a default was to instantiate ~pytest.Mark directly, which is private and warns.

• #​13369: Improved the error from pytest.RunResult.assert_outcomes when a plugin changes or removes pytest's standard terminal summary, and documented how to isolate output-changing plugins.

• #​13431: Exposed pytest.ParameterSet as the type of the return value of pytest.param().
  This can be used in type annotations and isinstance checks.

• #​13564: Issue a warning when fixtures are wrapped with a decorator that prevents
  correct discovery, including @classmethod above @pytest.fixture and
  @staticmethod above @pytest.fixture. Put @pytest.fixture above
  those decorators on test classes.

• #​14164: Exposed pytest.Approx as the type of the return value of pytest.approx().
  This can be used in type annotations and isinstance checks.

• #​14463: Assertion diffs for mappings now match up keys the way the compared mappings match them themselves.

  Key comparison goes through the mappings' key views instead of plain sets of their keys, so a mapping
  with its own notion of key equivalence, such as case-insensitive header mappings, no longer
  reports its common keys as missing on either side.

• #​14523: Large assertion comparison diffs are now built lazily and capped to the
  truncation budget, so a huge diff is no longer formatted in full just to
  be truncated. As a consequence, the truncation footer no longer
  reports the exact number of hidden lines.

• #​14687: The default fd-level output capturing (--capture=fd) now skips reading the capture buffer for tests which produce no output, reducing per-test overhead in large test suites.

• #​14724: --no-summary now only applies directly to pytest's own summary.

  The flag no longer skips the pytest_terminal_summary hook, so third-party
  plugins (for example coverage) can still write their terminal summaries.

• #​14751: parser.addini <pytest.Parser.addini> now also accepts type expressions for its type argument, in addition to the existing string tags: the plain Python types str, bool, int, float, a Literal of strings, and unions of these (for example int | str or int | Literal["auto"]).

• #​14754: pytest.approx() now rejects infinite relative tolerances for datetime.timedelta values with a clear ValueError instead of raising OverflowError.

• #​14791: The junit_family, junit_logging, junit_duration_report, console_output_style, empty_parameter_set_mark, assertion_text_diff_style and tmp_path_retention_policy configuration options are now registered with the set of values they accept: an invalid value now fails with a clean usage error instead of being silently ignored or crashing later, and pytest --help lists the accepted values.

  config.getini <pytest.Config.getini> now raises pytest.UsageError instead of TypeError or ValueError when the value read from the configuration file does not match the registered type, so a bad value is always reported as a short usage error message instead of an internal error traceback. Asking for an option name that was never registered still raises ValueError.

• #​15006: pytest.approx now emits pytest.PytestApproxDecimalToleranceWarning when a rel or abs tolerance is given as a float that cannot be represented exactly for a ~decimal.Decimal comparison, since such a tolerance is widened to the float's exact binary value.

• #​14675, #​14953, #​15153, #​15132: The truncation_limit_lines, truncation_limit_chars, max_warnings, verbosity_assertions, verbosity_test_cases, verbosity_subtests, tmp_path_retention_count, log_level, log_cli_level, log_file_level,log_auto_indent and faulthandler_timeout configuration options now accept native integer (and, for log_auto_indent, boolean) values in TOML configuration files, while still accepting strings for backward compatibility.
  log_file_mode now reports invalid values as a usage error.

• #​15254: tmp_path and TempPathFactory.mktemp <pytest.TempPathFactory.mktemp> no longer list the whole base temporary directory on every call, which made sessions with many temporary directories quadratically slow. Numbers are now handed out from a per-prefix counter, skipping names that already exist.

• #​4569: Node.add_marker <_pytest.nodes.Node.add_marker> now stores a ~pytest.Mark in node.keywords, matching what marks applied during collection store. Previously it stored a ~pytest.MarkDecorator.

• #​9436: Avoided formatting tracebacks for tests marked with xfail(run=False).

Bug fixes

• #​10128: Configured warning filters now apply to warnings emitted by pytest_configure hooks.

• #​10210: pytest.approx now raises a TypeError for any nested container, not
  only for one of the same type as its parent. Previously approx([{"k": 1}])
  and approx({"k": [1]}) were accepted and then compared unequal to every
  value, silently ignoring the tolerance, while approx([[1]]) correctly
  reported that nesting is unsupported.

• #​10644: monkeypatch.setattr() no longer leaves a new entry in the instance __dict__ when it patches an attribute that the instance inherits from its class.

  Previously undo() assigned the inherited value onto the instance, which shadowed the class attribute -- permanently freezing the result for descriptors that resolve dynamically.

• #​1139: Fixed tracebacks showing ??? instead of source lines for code compiled with a filename relative to a directory other than the current working directory -- e.g. compiled Cython modules, when running pytest from a subdirectory of the project root.
  The source lookup now falls back to searching sys.path for such filenames, as the standard traceback module does.

• #​11502: The rootdir is no longer derived from a configuration file that is not a regular file, such as --config-file=/dev/null.

• #​11783: Plugins installed in editable mode (660) are marked for assertion rewriting again.

  Such installs do not record the package's Python files in the distribution metadata, so pytest found nothing to rewrite and assertions inside the plugin lost their introspection. The plugin's entry point is now used to locate the package in that case.

• #​11933: pytest.warns no longer re-emits unmatched warnings with module="warnings", which caused module-based warning filters to be applied to the wrong warnings. Since warnings.WarningMessage does not record the module a warning was emitted with, re-emitted warnings now use the standard warnings.warn_explicit default of deriving the module from the warning's filename.

• #​12175: ExceptionInfo.exconly(tryshort=True) <pytest.ExceptionInfo.exconly> now strips the AssertionError: prefix of failed assert statements for ~pytest.ExceptionInfo objects created by pytest.raises, and failures inside unittest.TestCase.subTest report the same short crash line as regular tests.

• #​12223: The message attribute of <failure> and <error> elements in --junitxml reports is now shortened to whole lines within 500 characters. When something is dropped, it ends with a note pointing to the element text, which still holds the full report. Previously, very verbose assertion output (e.g. with -vv) produced attributes tens of thousands of characters long, which some XML parsers fail on.

• #​12307: Fixed truncation of long collections (lists, dicts, sets, etc.) in the "message" part of failed assertions (as in assert condition, msg) when using -vv: the message now uses the same unlimited repr as the rest of the assertion output, instead of eliding collection elements with ....

• #​12824: Custom command-line options now fail with a clear error when their implicit
  destination conflicts with an existing option, avoiding silent overrides of
  built-in options such as -k.

• #​13292: Fixed a stale rewritten module being used when a test file is modified twice
  within the same second without changing its size -- the pyc header could only
  record whole-second timestamps. The cache is now keyed on a hash of the source.

• #​14036: __tracebackhide__ is now respected in ExceptionGroup tracebacks, both for the group itself and for its sub-exceptions.

• #​14189: Nested usage of caplog.filtering <pytest.LogCaptureFixture.filtering> no longer removes filters early if they were already present.

• #​14412: Fixed incorrect timing information for subtests and parent tests when console_output_style = "times".

• #​14445: Assertion rewriting no longer evaluates walrus operator (:=) expressions more than once, which reported results the test never computed when the expression had side effects.

  An operand evaluated before a later walrus is now reported with the value it actually saw, so assert value != identity(value := value.lower()) keeps Python's left-to-right order.

• #​14552: Fixed stale co_filename values after a test module or directory is moved. Assertion-rewrite caches are reused when the source hash still matches, and in-memory code objects are pointed at the current path.

• #​14586: Negative values passed to log_auto_indent now correctly fall back to no indentation, matching the documented behavior.

• #​14619: Fixed a crash in pytest.mark.parametrize when a non-sequence value is passed for a parameter set. It now provides a clear error message during collection.

• #​14635: Fixed fixture resolution failures when specifying multiple test paths on the command line that share common parent directories. Parametrized fixtures defined in a conftest.py could be silently dropped depending on the order of the specified paths.

• #​14637: Pytest now correctly skips identical trailing characters in assertion text diffs even when the compared strings differ at the beginning.

• #​14638: Top-level options in pytest.toml and .pytest.toml files now raise an error instead of being silently ignored when no [pytest] table is present.

• #​14683: Fixed a regression in pytest 9.1 where a conftest.py located in the rootdir was no longer visible to tests and doctests collected from outside the rootdir (for example when passing a parent directory of the rootdir as a collection argument, or setting --rootdir to a subdirectory).

  As a result, fixtures defined in such a conftest -- including doctest_namespace injections -- were not available, causing errors such as NameError in doctests.

• #​14700: Fixed an internal error on Python 3.12 when a doctest on a fixture-decorated function was skipped.

• #​14705: TOML configuration files passed via -c now also read their configuration from the [pytest] table, the one pytest's own configuration files use. The [tool.pytest] and [tool.pytest.ini_options] tables such files were previously restricted to keep working; using both styles in one file is an error.

• #​14828: Exception groups raised from another exception now print their cause chain only once in the traceback output.

• #​14864: Fixed collection on Windows collecting the whole suite instead of the given path, on file systems which do not support file IDs (st_ino is 0 for every file, as seen for example on sshfs-win/WinFsp mounts).

• #​14884: Cache.get(), Cache.set() and Cache.mkdir() now reject keys that resolve outside the cache directory, and --cache-show ignores glob matches outside it.

• #​14909: Fixed MonkeyPatch.delattr <pytest.MonkeyPatch.delattr>, MonkeyPatch.setitem <pytest.MonkeyPatch.setitem> and MonkeyPatch.delitem <pytest.MonkeyPatch.delitem> recording a stale undo entry when the underlying mutation failed, which could cause spurious errors during teardown. The undo entry is now recorded only after the mutation succeeds, matching the behavior of MonkeyPatch.setattr <pytest.MonkeyPatch.setattr>.

• #​14912: ~pytest.PytestWarning instances defined in _pytest.deprecated are no longer reused across warnings.warn calls, so warnings raised as errors (e.g. with -W error) no longer accumulate stale traceback frames from previous raises.

• #​14942: Fixed a regression in 9.1.0 that made collection very slow (quadratic) when many fixtures are defined with the same name.
  This can happen particularly when many tests are defined in separate classes which inherit from a base class which defines fixtures (the fixtures are repeated per class).

• #​15005: pytest.approx no longer treats finite ~decimal.Decimal values outside the float range (such as Decimal("1e400")) as infinite, which made in-tolerance comparisons fail.

• #​15006: Restored the tolerance shown by pytest.approx for ~decimal.Decimal values, which since 9.0 displayed ??? for the default tolerance and reported the raw rel ratio instead of the absolute tolerance actually compared against.

• #​15006: The failure message for pytest.approx comparisons of ~decimal.Decimal collections no longer reports Max absolute difference: -inf, or crashes for mappings, when the decimal.FloatOperation trap is set.

• #​15006: pytest.approx no longer raises AttributeError when comparing numpy.ndarray instances with object dtype, such as arrays of ~decimal.Decimal.

• #​15032: Help texts for command-line options and configuration options now keep their indentation
  and blank lines. Previously each line was stripped before wrapping, so a wrapped
  list item was indistinguishable from a new one and blank lines were dropped; configuration
  option help lost its line breaks entirely.

• #​15043: Cache writes now emit pytest.PytestCacheWarning when writing or closing the cache file fails, consistent with errors opening the file.

• #​15052: Fixed possible off-by-one line numbers in --fixtures and --fixtures-per-test output.

• #​15145: With console_output_style set to times, durations just below a unit boundary are now shown in the next unit (e.g. 1.000ms instead of 1000.0us).

• #​15172: Assertion diffs now pretty-print the built-in frozendict (Python 3.15+) across multiple lines, similarly to how dict is displayed.

• #​4569: -k no longer matches attributes that end up in a test function's __dict__ without being meant as keywords, such as pytest's own pytestmark attribute and the bookkeeping left behind by functools.wraps and functools.lru_cache.

• #​6750: Fix fixture argument discovery for custom collectors that pass bound methods to pytest.Function.

• #​6997: XFAIL reports from teardown phases now include the phase in the short test
  summary.

• #​7940: Fixed cleanup of temporary directories failing when subdirectories have their execute permission removed.

• #​8321: Fixed exception chains being duplicated in the traceback output when an exception in the chain (__cause__/__context__) has no traceback of its own, and that exception is itself linked to further exceptions.

• #​8914: Tests parametrized with higher-than-function scope are now reordered by
  parameter value rather than by parameter index, so that items using equal
  parameter values are grouped together and share a single fixture setup, even
  when they are parametrized by separate @pytest.mark.parametrize <pytest.mark.parametrize ref>
  calls. Previously, an expensive higher-scoped fixture could be set up and torn
  down repeatedly for the same parameter value.

  Unhashable parameter values (e.g. dicts) keep the previous index-based
  grouping behavior.

  As a consequence, the order in which parametrized tests run may change
  (fixture setup/teardown counts can only decrease, not increase).

• #​9924: Fixed doctest option flags leaking between docstrings after a failure, skip, or expected failure.

Improved documentation

• #​10721: Replaced setup.py usage with pyproject.toml in writing-plugins.
• #​12658: Moved the fixture setup and finalizer hooks to the test running hooks section in the reference documentation.
• #​12857: Documented how --confcutdir affects initial conftest.py discovery.
• #​14157: Added the pytest-flakefighters plugin to the list of flaky test plugins in plugins.rst.
  Added flaky test papers published on the Test FLARE project to the list of flaky papers in plugins.rst.
• #​15127: Added guidance on typing yield fixtures, including annotating fixture functions with their generator type and fixture consumers with the yielded value type.
• #​15242: The installation instructions <installation> and install-package-with-pip now show how to install pytest into a virtual environment with venv and pip, uv or virtualenv, and explain the externally-managed-environment error.
• #​4569: pytest --help, the -k reference entry and select-tests no longer describe -k as a Python expression matched against test names only; keyword expressions now shows marker names being matched as well. The examples that looked up a marker use Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> rather than item.keywords.
• #​9614: Clarified that session.items and session.testscollected exclude deselected tests in the pytest_collection documentation.

Packaging updates and notes for downstreams

• #​11680: Source archives of arbitrary commits -- the tarballs GitHub serves under
  /archive/, not just the ones for tags -- can now be built into an sdist or a
  wheel with a correct version. A .git_archival.txt file, expanded by git archive via export-subst, carries the describe output that
  setuptools-scm would otherwise have to ask git for.

  The archival file deliberately omits ref-names. Recording it would make the
  content of an archive -- and therefore its checksum -- change whenever a branch
  that points at the archived commit is moved afterwards, which is how the
  equivalent tarballs of tagged releases became unstable for other projects.
  Describe output alone depends only on the commit and on the tags reachable from
  it.

  The archival file is not shipped in the sdist -- an sdist carries its version
  in its metadata, and the template is only ever expanded by git archive.

  Building pytest from a git checkout now requires setuptools-scm >= 10.1.

• #​9236: pluggy>=1.6 is now required.

  Older pluggy versions stopped running the remaining hook wrapper teardowns once an
  old-style hookwrapper raised in its own teardown. The logging plugin's wrapper was
  left suspended, and when it was finalised later it detached the handler that
  caplog of a subsequent test was recording through, so that test saw no records.

Contributor-facing changes

• #​14813: Added a systematic coverage matrix for assertion rewriting.
• #​14921: Added scripts/diff-assert-rewrite.py, which diffs the assert-rewritten form of a snippet between the plain source, this checkout and released pytest versions.
• #​15190: Fixed the documentation build with Pluggy 1.7 by ignoring a reference to its undocumented DistFacade compatibility class.

Miscellaneous internal changes

• #​13888: FixtureRequest.node <pytest.FixtureRequest.node> is now explicitly annotated as returning Any, so strict pyright no longer reports it as Unknown. The return type stays deliberately broad, see 13888.
• #​14758: Internal node ids (the ::-separated strings identifying collected items, e.g. path/to/test_file.py::TestClass::test_method[param]) are now represented internally by a single structured ~_pytest.nodeid.NodeId dataclass instead of being repeatedly re-parsed as plain strings. The public nodeid: str attribute on nodes and reports is unchanged and remains fully backward compatible for plugins.

v9.1.1

Compare Source

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.

v9.1.0

Compare Source

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.
  The same functionality is now available in an external plugin, pytest-pastebin.
  See pastebin-deprecated for more details.

• #​14513: The private FixtureDef.has_location attribute is now deprecated and will be removed in pytest 10.
  See fixturedef-has-location-deprecated for details.

• #​1764: pytest.console_main is now deprecated and will be removed in pytest 10.
  It was never intended for programmatic use; use pytest.main instead.

New features

• #​12376: Added pytest.register_fixture() to register fixtures using an imperative interface.

  This is an advanced function intended for use by plugins.

  Normally, fixtures should be registered declaratively using the @pytest.fixture <pytest.fixture> decorator.
  Pytest looks for these fixture definitions during the collection phase and registers them automatically.
  For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used.

• #​14023: Added --report-chars long CLI option.

• #​14371: Added --max-warnings command-line option and max_warnings configuration option to fail the test run when the number of warnings exceeds a given threshold -- by miketheman.

• #​6757: Added the assertion_text_diff_style configuration option, allowing
  string equality failures to be rendered as separate Left: and Right:
  blocks instead of ndiff output.

• #​8395: Added support for ~datetime.datetime and ~datetime.timedelta comparisons with pytest.approx. An explicit abs or rel tolerance as a ~datetime.timedelta is required and relative tolerance is not supported for datetime comparisons -- by hamza-mobeen.

Improvements in existing functionality

• #​11225: pytest.warns now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the match pattern did not match.

• #​11295: Improved output of --fixtures-per-test by excluding internal-implementation fixtures generated by @pytest.mark.parametrize and similar.

• #​13241: pytest.raises, pytest.warns and pytest.deprecated_call now uses ParamSpec for the type hint to the (old and not recommended) callable overload, instead of Any. This allows type checkers to raise errors when passing incorrect function parameters.
  func can now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept.

• #​13862: Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr.

• #​14026: Added test coverage for compiled regex patterns in pytest.raises match parameter.

• #​14137: pytest.ScopeName is now public to allow using it in function signatures.

• #​14342: Marked yield_fixture as deprecated to type checkers using the deprecated decorator. Note it
  has originally been deprecated <yield-fixture-deprecated> in pytest 6.2 already.

• #​14373: Added type annotations for pytest.approx.

• #​14430: When using --setup-show, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result.

• #​14441: Reduced the default number of gc.collect() passes in the unraisableexception plugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via __del__. This can noticeably speed up test suites that trigger many pytester runs.

• #​14461: Improved assertion failure ex

[!IMPORTANT]
✂ PR body was truncated to here.

[renovate-ce-it-martin-bens]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml

Artifact update for typos resolved to version 1.52.0, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.51.1
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/