all:
  children:
    zuul_unreachable:
      hosts: {}
  hosts:
    debian-bookworm:
      ansible_connection: ssh
      ansible_host: 2a13:1a81:8000:3124:f816:3eff:feae:d1c2
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      nodepool:
        az: nova
        cloud: regiocloud-a-ci
        external_id: 8ef2117d-2bcf-4d64-bce6-eba2cd5c24cf
        host_id: 82101243836454d7401d5893feae9e2c5df7cc291646d8a99b33b53b
        interface_ip: 2a13:1a81:8000:3124:f816:3eff:feae:d1c2
        label: debian-bookworm
        node_properties: {}
        private_ipv4: 10.128.0.101
        private_ipv6: null
        provider: regiocloud-a
        public_ipv4: 81.163.193.238
        public_ipv6: 2a13:1a81:8000:3124:f816:3eff:feae:d1c2
        region: null
        slot: null
  vars:
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-config/zuul.d/jobs.yaml@main#2>'
      - '<Job flake8 explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: osism/zuul-jobs/.zuul.yaml@main#32>'
      - '<Job flake8 explicit: None implied: None source: osism/ansible-collection-services/.zuul.yaml@main#498>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: 522ded43842c45cb816e3fa48e02801e
      build_refs:
      - branch: main
        change: '2103'
        change_message: "chore(deps): update dependency pytest to v9\n\nThis PR contains
          the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
          [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
          | `==8.4.2` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/8.4.2/9.1.0?slim=true)
          |\n\n---\n\n> [!WARNING]\n> Some dependencies could not be looked up. Check
          the [Dependency Dashboard](../issues/293) for more information.\n\n---\n\n###
          Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
          [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
          pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
          changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  If this is undesirable,
          move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
          explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
          pytest possibly collects Python modules twice, once as `pytest.Module` and
          once as a `DoctestModule` (depending on the configuration).\n  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`.\n  This
          means that both need to register the fixtures independently.\n\n##### Deprecations
          (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n  See `10819` and
          `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  See `dynamic-fixture-request-during-teardown`
          for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  These iterables get exhausted after the first iteration,\n
          \ leading to tests getting unexpectedly skipped in cases such as running
          `pytest.main()` multiple times,\n  using class-level parametrize decorators,\n
          \ or collecting tests multiple times.\n\n  See `parametrize-iterators` for
          details and suggestions.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
          <pytest.Config.getini>` to access configuration values instead.\n\n  See
          `config-inicfg` for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  Use the `node` parameter instead for fixture
          scoping. This enables more robust node-based\n  matching instead of string
          prefix matching.\n  If you've used `nodeid=None`, pass `node=session` instead.\n\n
          \ This will be removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
          The method of configuring hooks using markers, deprecated since pytest 7.2,
          is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
          details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
          The `--pastebin` option is now deprecated.\n  The same functionality is
          now available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
          for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The private `FixtureDef.has_location` attribute is now deprecated and will
          be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for
          details.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
          \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
          New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
          Added `pytest.register_fixture()` to register fixtures using an imperative
          interface.\n\n  This is an advanced function intended for use by plugins.\n\n
          \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
          <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
          during the collection phase and registers them automatically.\n  For some
          plugin usecases the declarative interface can be cumbersome or unviable,
          in which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
          Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
          [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
          Added the `assertion_text_diff_style` configuration option, allowing\n  string
          equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
          instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n##### Improvements in existing functionality\n\n-
          [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
          [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
          Improved output of `--fixtures-per-test` by excluding internal-implementation
          fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/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.\n  `func` can now also be passed as a kwarg, which
          the type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
          Improved the readability of \"DID NOT RAISE\" error messages by using the
          exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
          [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
          Added test coverage for compiled regex patterns in `pytest.raises` match
          parameter.\n\n- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
          <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow
          using it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
          Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
          decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
          in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
          Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
          [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
          Improved assertion failure explanations for equality comparisons between
          mapping objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The order in which fixture definitions overriding each other are resolved
          is now determined first by their *visibility* in the collection tree rather
          than by the order in which they are registered.\n\n  A fixture defined for
          a more specific node (e.g. a module or an item) now always takes precedence
          over one with the same name defined for a more general node (e.g. the session),
          even when the more general one was registered later.\n  Fixtures with non-comparable
          visibility or the same visibility keep the existing behavior of \"last registered
          wins\".\n  This change is supposed to only affect plugins which register
          multiple fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
          Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          Improved argparse program name to show `pytest`, `python -m pytest`, or
          `pytest.main()` based on how pytest was invoked, making help and error messages
          clearer.\n\n- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
          Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
          `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
          this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
          pytest issues a helpful warning and continues collecting the module normally.\n\n#####
          Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
          Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
          meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
          [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
          Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
          [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
          Fixed function-scoped fixture values being kept alive after a test was interrupted
          by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be
          released more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
          Fixed `capteesys` producing doubled output when used with `--capture=no`
          (`-s`).\n\n- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
          Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
          the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
          Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
          being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
          Fixed autouse fixtures defined inside a `unittest.TestCase` class running
          even when the class is decorated with `unittest.skip` or `unittest.skipIf`
          -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
          `unittest.SkipTest` is no longer considered an interactive exception, i.e.
          `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
          Fixed subtests running with `pytest-xdist` when their contexts contain objects
          that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
          [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Fixed conftest.py fixture scoping when `testpaths` points outside of the
          `rootdir <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files
          would incorrectly leak to sibling directories\n  when using a relative `testpaths`
          like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
          <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
          [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
          Display dictionary differences in assertion failures using the original
          key insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
          fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
          methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
          An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
          from being torn down, causing additional errors in the following tests.\n\n-
          [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
          Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
          entry on the undo stack when the underlying `setattr()` call fails (e.g.
          on immutable targets), causing an `AttributeError` crash during teardown.\n\n-
          [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
          Fixed `-v` hint in `pytest.raises` match diff not working because assertion
          verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
          Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
          <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
          Fixed direct parametrization causing the static fixture closure (as reflected
          in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit
          fixtures that are requested transitively from overridden fixtures.\n\n-
          [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
          Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
          before pytest tears down the warning filters installed for the session.
          Previously the collection ran from a cleanup callback whose order relative
          to other plugins' cleanups was not guaranteed, so an active `error` filter
          could be removed before the exception surfaced and a late resource leak
          would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
          now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
          [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
          Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
          when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
          [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
          Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
          [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
          Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
          the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
          [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
          Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
          detection, causing the regex diff display to be shown in some instances
          when the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
          Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
          specified through `addopts` were silently ignored.\n\n  Note that when targeting
          pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
          `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
          Fixed `pytest.approx` not recognizing types with `__array_interface__` as
          numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
          Fixed a regression where `-k` and `-m` expressions containing both backslash
          characters in identifiers and string literal arguments would incorrectly
          raise a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
          Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
          plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
          [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
          Fixed `Code.getargs()` incorrectly including local variable names in the
          returned argument tuple for functions with `*args` and/or `**kwargs`. The
          method was using `co_flags` bitmask values (`4` and `8`) directly as counts
          instead of converting them to `1` via `bool()`, and was not accounting for
          `co_kwonlyargcount` when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
          Logging capture now works for non-propagating loggers.\n  Previously only
          logs which reached the root logger were captured.\n  This includes `caplog`
          and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
          Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
          now always matches the number of `<testcase>` elements in the file. In some
          cases (test passes but fails during teardown) the `tests` attribute would
          report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
          `pytest_fixture_post_finalizer` is no longer called extra times for the
          same fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
          Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
          single-element tuple values when using a string argnames with a trailing
          comma (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves
          like the tuple form `(\"arg\",)`, treating argvalues as a list of tuples
          to unpack.\n\n##### Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
          Document safer alternatives and scope guidance for monkeypatching standard
          library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
          Document that `@pytest.hookimpl(specname=...)` only works for function names
          starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
          Document that doctests do not support parametrized fixtures, including parametrized
          autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
          Clarified how the `request` fixture provides indirect parametrization values
          via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
          Clarified in the documentation that hook implementations defined in `conftest.py`
          files are not available to other plugins during their `pytest_addoption()`
          execution, as conftest files are discovered and loaded after builtin and
          third-party plugins have been initialized. However, initial conftest files
          themselves can implement `pytest_addoption()` to add their own command-line
          options.\n- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
          Clarified how subtest progress markers are shown in the documentation.\n-
          [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
          The `ini options ref` section of the API Reference now specified the type
          and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
          Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
          plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
          The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
          Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
          at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
          Pointing at a tag keeps the example in sync with the version users actually
          install, while remaining stable when the project's main branch moves on.\n\n#####
          Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
          Improved the recursion traceback test to exercise all requested traceback
          styles.\n\n### [`v9.0.3`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.3)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.2...9.0.3)\n\n###
          pytest 9.0.3 (2026-04-07)\n\n#### Bug fixes\n\n- [#&#8203;12444](https://redirect.github.com/pytest-dev/pytest/issues/12444):
          Fixed `pytest.approx` which now correctly takes into account `~collections.abc.Mapping`
          keys order to compare them.\n\n- [#&#8203;13634](https://redirect.github.com/pytest-dev/pytest/issues/13634):
          Blocking a `conftest.py` file using the `-p no:` option is now explicitly
          disallowed.\n\n  Previously this resulted in an internal assertion failure
          during plugin loading.\n\n  Pytest now raises a clear `UsageError` explaining
          that conftest files are not plugins and cannot be disabled via `-p`.\n\n-
          [#&#8203;13734](https://redirect.github.com/pytest-dev/pytest/issues/13734):
          Fixed crash when a test raises an exceptiongroup with `__tracebackhide__
          = True`.\n\n- [#&#8203;14195](https://redirect.github.com/pytest-dev/pytest/issues/14195):
          Fixed an issue where non-string messages passed to <span class=\"title-ref\">unittest.TestCase.subTest()</span>
          were not printed.\n\n- [#&#8203;14343](https://redirect.github.com/pytest-dev/pytest/issues/14343):
          Fixed use of insecure temporary directory (CVE-2025-71176).\n\n#### Improved
          documentation\n\n- [#&#8203;13388](https://redirect.github.com/pytest-dev/pytest/issues/13388):
          Clarified documentation for `-p` vs `PYTEST_PLUGINS` plugin loading and
          fixed an incorrect `-p` example.\n- [#&#8203;13731](https://redirect.github.com/pytest-dev/pytest/issues/13731):
          Clarified that capture fixtures (e.g. `capsys` and `capfd`) take precedence
          over the `-s` / `--capture=no` command-line options in `Accessing captured
          output from a test function <accessing-captured-output>`.\n- [#&#8203;14088](https://redirect.github.com/pytest-dev/pytest/issues/14088):
          Clarified that the default `pytest_collection` hook sets `session.items`
          before it calls `pytest_collection_finish`, not after.\n- [#&#8203;14255](https://redirect.github.com/pytest-dev/pytest/issues/14255):
          TOML integer log levels must be quoted: Updating reference documentation.\n\n####
          Contributor-facing changes\n\n- [#&#8203;12689](https://redirect.github.com/pytest-dev/pytest/issues/12689):
          The test reports are now published to Codecov from GitHub Actions.\n  The
          test statistics is visible [on the web interface](https://app.codecov.io/gh/pytest-dev/pytest/tests).\n\n
          \ \\-- by `aleguy02`\n\n### [`v9.0.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.2)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.1...9.0.2)\n\n###
          pytest 9.0.2 (2025-12-06)\n\n#### Bug fixes\n\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
          The terminal progress feature added in pytest 9.0.0 has been disabled by
          default, except on Windows, due to compatibility issues with some terminal
          emulators.\n\n  You may enable it again by passing `-p terminalprogress`.
          We may enable it by default again once compatibility improves in the future.\n\n
          \ Additionally, when the environment variable `TERM` is `dumb`, the escape
          codes are no longer emitted, even if the plugin is enabled.\n\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
          Fixed the TOML type of the `tmp_path_retention_count` settings in the API
          reference from number to string.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute was changed in a breaking manner in
          pytest 9.0.0.\n  Due to its usage in the ecosystem, it is now restored to
          working order using a compatibility shim.\n  It will be deprecated in pytest
          9.1 and removed in pytest 10.\n\n- [#&#8203;13965](https://redirect.github.com/pytest-dev/pytest/issues/13965):
          Fixed quadratic-time behavior when handling `unittest` subtests in Python
          3.10.\n\n#### Improved documentation\n\n- [#&#8203;4492](https://redirect.github.com/pytest-dev/pytest/issues/4492):
          The API Reference now contains cross-reference-able documentation of `pytest's
          command-line flags <command-line-flags>`.\n\n### [`v9.0.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.1)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.0...9.0.1)\n\n###
          pytest 9.0.1 (2025-11-12)\n\n#### Bug fixes\n\n- [#&#8203;13895](https://redirect.github.com/pytest-dev/pytest/issues/13895):
          Restore support for skipping tests via `raise unittest.SkipTest`.\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
          The terminal progress plugin added in pytest 9.0 is now automatically disabled
          when iTerm2 is detected, it generated desktop notifications instead of the
          desired functionality.\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
          Fixed the TOML type of the verbosity settings in the API reference from
          number to string.\n- [#&#8203;13910](https://redirect.github.com/pytest-dev/pytest/issues/13910):
          Fixed <span class=\"title-ref\">UserWarning: Do not expect file\\_or\\_dir</span>
          on some earlier Python 3.12 and 3.13 point versions.\n\n#### Packaging updates
          and notes for downstreams\n\n- [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
          The tox configuration has been adjusted to make sure the desired\n  version
          string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
          environment\n  variable as a part of the release process -- by `webknjaz`.\n\n####
          Contributor-facing changes\n\n- [#&#8203;13891](https://redirect.github.com/pytest-dev/pytest/issues/13891),
          [#&#8203;13942](https://redirect.github.com/pytest-dev/pytest/issues/13942):
          The CI/CD part of the release automation is now capable of\n  creating GitHub
          Releases without having a Git checkout on\n  disk -- by `bluetech` and `webknjaz`.\n-
          [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
          The tox configuration has been adjusted to make sure the desired\n  version
          string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
          environment\n  variable as a part of the release process -- by `webknjaz`.\n\n###
          [`v9.0.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/8.4.2...9.0.0)\n\n###
          pytest 9.0.0 (2025-11-05)\n\n#### New features\n\n- [#&#8203;1367](https://redirect.github.com/pytest-dev/pytest/issues/1367):
          **Support for subtests** has been added.\n\n  `subtests <subtests>` are
          an alternative to parametrization, useful in situations where the parametrization
          values are not all known at collection time.\n\n  Example:\n\n  ```python\n
          \ def contains_docstring(p: Path) -> bool:\n      \"\"\"Return True if the
          given Python file contains a top-level docstring.\"\"\"\n      ...\n\n  def
          test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:\n      for
          path in Path.cwd().glob(\"*.py\"):\n          with subtests.test(path=str(path)):\n
          \             assert contains_docstring(path)\n  ```\n\n  Each assert failure
          or error is caught by the context manager and reported individually, giving
          a clear picture of all files that are missing a docstring.\n\n  In addition,
          `unittest.TestCase.subTest` is now also supported.\n\n  This feature was
          originally implemented as a separate plugin in [pytest-subtests](https://redirect.github.com/pytest-dev/pytest-subtests),
          but since then has been merged into the core.\n\n  > \\[!NOTE]\n  > This
          feature is experimental and will likely evolve in future releases. By that
          we mean that we might change how subtests are reported on failure, but the
          functionality and how to use it are stable.\n\n- [#&#8203;13743](https://redirect.github.com/pytest-dev/pytest/issues/13743):
          Added support for **native TOML configuration files**.\n\n  While pytest,
          since version 6, supports configuration in `pyproject.toml` files under
          `[tool.pytest.ini_options]`,\n  it does so in an \"INI compatibility mode\",
          where all configuration values are treated as strings or list of strings.\n
          \ Now, pytest supports the native TOML data model.\n\n  In `pyproject.toml`,
          the native TOML configuration is under the `[tool.pytest]` table.\n\n  ```toml\n
          \ # pyproject.toml\n  [tool.pytest]\n  minversion = \"9.0\"\n  addopts =
          [\"-ra\", \"-q\"]\n  testpaths = [\n      \"tests\",\n      \"integration\",\n
          \ ]\n  ```\n\n  The `[tool.pytest.ini_options]` table remains supported,
          but both tables cannot be used at the same time.\n\n  If you prefer to use
          a separate configuration file, or don't use `pyproject.toml`, you can use
          `pytest.toml` or `.pytest.toml`:\n\n  ```toml\n  # pytest.toml or .pytest.toml\n
          \ [pytest]\n  minversion = \"9.0\"\n  addopts = [\"-ra\", \"-q\"]\n  testpaths
          = [\n      \"tests\",\n      \"integration\",\n  ]\n  ```\n\n  The documentation
          now (sometimes) shows configuration snippets in both TOML and INI formats,
          in a tabbed interface.\n\n  See `config file formats` for full details.\n\n-
          [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
          Added a **\"strict mode\"** enabled by the `strict` configuration option.\n\n
          \ When set to `true`, the `strict` option currently enables\n\n  - `strict_config`\n
          \ - `strict_markers`\n  - `strict_parametrization_ids`\n  - `strict_xfail`\n\n
          \ The individual strictness options can be explicitly set to override the
          global `strict` setting.\n\n  The previously-deprecated `--strict` command-line
          flag now enables strict mode.\n\n  If pytest adds new strictness options
          in the future, they will also be enabled in strict mode.\n  Therefore, you
          should only enable strict mode if you use a pinned/locked version of pytest,\n
          \ or if you want to proactively adopt new strictness options as they are
          added.\n\n  See `strict mode` for more details.\n\n- [#&#8203;13737](https://redirect.github.com/pytest-dev/pytest/issues/13737):
          Added the `strict_parametrization_ids` configuration option.\n\n  When set,
          pytest emits an error if it detects non-unique parameter set IDs,\n  rather
          than automatically making the IDs unique by adding <span class=\"title-ref\">0</span>,
          <span class=\"title-ref\">1</span>, ... to them.\n  This can be particularly
          useful for catching unintended duplicates.\n\n- [#&#8203;13072](https://redirect.github.com/pytest-dev/pytest/issues/13072):
          Added support for displaying test session **progress in the terminal tab**
          using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC)
          ANSI sequence.\n  When pytest runs in a supported terminal emulator like
          ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,\n  you'll
          see the progress in the terminal tab or window,\n  allowing you to monitor
          pytest's progress at a glance.\n\n  This feature is automatically enabled
          when running in a TTY. It is implemented as an internal plugin. If needed,
          it can be disabled as follows:\n\n  - On a user level, using `-p no:terminalprogress`
          on the command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`.\n
          \ - On a project configuration level, using `addopts = \"-p no:terminalprogress\"`.\n\n-
          [#&#8203;478](https://redirect.github.com/pytest-dev/pytest/issues/478):
          Support PEP420 (implicit namespace packages) as <span class=\"title-ref\">--pyargs</span>
          target when `consider_namespace_packages` is <span class=\"title-ref\">true</span>
          in the config.\n\n  Previously, this option only impacted package imports,
          now it also impacts tests discovery.\n\n- [#&#8203;13678](https://redirect.github.com/pytest-dev/pytest/issues/13678):
          Added a new `faulthandler_exit_on_timeout` configuration option set to \"false\"
          by default to let <span class=\"title-ref\">faulthandler</span> interrupt
          the <span class=\"title-ref\">pytest</span> process after a timeout in case
          of deadlock.\n\n  Previously, a <span class=\"title-ref\">faulthandler</span>
          timeout would only dump the traceback of all threads to stderr, but would
          not interrupt the <span class=\"title-ref\">pytest</span> process.\n\n  \\--
          by `ogrisel`.\n\n- [#&#8203;13829](https://redirect.github.com/pytest-dev/pytest/issues/13829):
          Added support for configuration option aliases via the `aliases` parameter
          in `Parser.addini() <pytest.Parser.addini>`.\n\n  Plugins can now register
          alternative names for configuration options,\n  allowing for more flexibility
          in configuration naming and supporting backward compatibility when renaming
          options.\n  The canonical name always takes precedence if both the canonical
          name and an alias are specified in the configuration file.\n\n#### Improvements
          in existing functionality\n\n- [#&#8203;13330](https://redirect.github.com/pytest-dev/pytest/issues/13330):
          Having pytest configuration spread over more than one file (for example
          having both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]`
          table) will now print a warning to make it clearer to the user that only
          one of them is actually used.\n\n  \\-- by `sgaist`\n\n- [#&#8203;13574](https://redirect.github.com/pytest-dev/pytest/issues/13574):
          The single argument `--version` no longer loads the entire plugin infrastructure,
          making it faster and more reliable when displaying only the pytest version.\n\n
          \ Passing `--version` twice (e.g., `pytest --version --version`) retains
          the original behavior, showing both the pytest version and plugin information.\n\n
          \ > \\[!NOTE]\n  > Since `--version` is now processed early, it only takes
          effect when passed directly via the command line. It will not work if set
          through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`.\n\n- [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
          Added `strict_xfail` as an alias to the `xfail_strict` option,\n  `strict_config`
          as an alias to the `--strict-config` flag,\n  and `strict_markers` as an
          alias to the `--strict-markers` flag.\n  This makes all strictness options
          consistently have configuration options with the prefix `strict_`.\n\n-
          [#&#8203;13700](https://redirect.github.com/pytest-dev/pytest/issues/13700):
          <span class=\"title-ref\">--junitxml</span> no longer prints the <span class=\"title-ref\">generated
          xml file</span> summary at the end of the pytest session when <span class=\"title-ref\">--quiet</span>
          is given.\n\n- [#&#8203;13732](https://redirect.github.com/pytest-dev/pytest/issues/13732):
          Previously, when filtering warnings, pytest would fail if the filter referenced
          a class that could not be imported. Now, this only outputs a message indicating
          the problem.\n\n- [#&#8203;13859](https://redirect.github.com/pytest-dev/pytest/issues/13859):
          Clarify the error message for <span class=\"title-ref\">pytest.raises()</span>
          when a regex <span class=\"title-ref\">match</span> fails.\n\n- [#&#8203;13861](https://redirect.github.com/pytest-dev/pytest/issues/13861):
          Better sentence structure in a test's expected error message. Previously,
          the error message would be \"expected exception must be \\<expected>, but
          got \\<actual>\". Now, it is \"Expected \\<expected>, but got \\<actual>\".\n\n####
          Removals and backward incompatible breaking changes\n\n- [#&#8203;12083](https://redirect.github.com/pytest-dev/pytest/issues/12083):
          Fixed a bug where an invocation such as <span class=\"title-ref\">pytest
          a/ a/b</span> would cause only tests from <span class=\"title-ref\">a/b</span>
          to run, and not other tests under <span class=\"title-ref\">a/</span>.\n\n
          \ The fix entails a few breaking changes to how such overlapping arguments
          and duplicates are handled:\n\n  1. <span class=\"title-ref\">pytest a/b
          a/</span> or <span class=\"title-ref\">pytest a/ a/b</span> are equivalent
          to <span class=\"title-ref\">pytest a</span>; if an argument overlaps another
          arguments, only the prefix remains.\n  2. <span class=\"title-ref\">pytest
          x.py x.py</span> is equivalent to <span class=\"title-ref\">pytest x.py</span>;
          previously such an invocation was taken as an explicit request to run the
          tests from the file twice.\n\n  If you rely on these behaviors, consider
          using `--keep-duplicates <duplicate-paths>`, which retains its existing
          behavior (including the bug).\n\n- [#&#8203;13719](https://redirect.github.com/pytest-dev/pytest/issues/13719):
          Support for Python 3.9 is dropped following its end of life.\n\n- [#&#8203;13766](https://redirect.github.com/pytest-dev/pytest/issues/13766):
          Previously, pytest would assume it was running in a CI/CD environment if
          either of the environment variables <span class=\"title-ref\">$CI</span>
          or <span class=\"title-ref\">$BUILD\\_NUMBER</span> was defined;\n  now,
          CI mode is only activated if at least one of those variables is defined
          and set to a *non-empty* value.\n\n- [#&#8203;13779](https://redirect.github.com/pytest-dev/pytest/issues/13779):
          **PytestRemovedIn9Warning deprecation warnings are now errors by default.**\n\n
          \ Following our plan to remove deprecated features with as little disruption
          as\n  possible, all warnings of type `PytestRemovedIn9Warning` now generate
          errors\n  instead of warning messages by default.\n\n  **The affected features
          will be effectively removed in pytest 9.1**, so please consult the\n  `deprecations`
          section in the docs for directions on how to update existing code.\n\n  In
          the pytest `9.0.X` series, it is possible to change the errors back into
          warnings as a\n  stopgap measure by adding this to your `pytest.ini` file:\n\n
          \ ```ini\n  [pytest]\n  filterwarnings =\n      ignore::pytest.PytestRemovedIn9Warning\n
          \ ```\n\n  But this will stop working when pytest `9.1` is released.\n\n
          \ **If you have concerns** about the removal of a specific feature, please
          add a\n  comment to `13779`.\n\n#### Deprecations (removal in next major
          release)\n\n- [#&#8203;13807](https://redirect.github.com/pytest-dev/pytest/issues/13807):
          `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now
          issues a deprecation warning when the prepended path contains legacy namespace
          packages (those using `pkg_resources.declare_namespace()`).\n  Users should
          migrate to native namespace packages (`420`).\n  See `monkeypatch-fixup-namespace-packages`
          for details.\n\n#### Bug fixes\n\n- [#&#8203;13445](https://redirect.github.com/pytest-dev/pytest/issues/13445):
          Made the type annotations of `pytest.skip` and friends more spec-complaint
          to have them work across more type checkers.\n\n- [#&#8203;13537](https://redirect.github.com/pytest-dev/pytest/issues/13537):
          Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in
          teardown was not handled correctly and showed as error.\n\n- [#&#8203;13598](https://redirect.github.com/pytest-dev/pytest/issues/13598):
          Fixed possible collection confusion on Windows when short paths and symlinks
          are involved.\n\n- [#&#8203;13716](https://redirect.github.com/pytest-dev/pytest/issues/13716):
          Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file
          cannot be parametrized) was silently treated as `pytest x.py`. This is now
          a usage error.\n\n- [#&#8203;13722](https://redirect.github.com/pytest-dev/pytest/issues/13722):
          Fixed a misleading assertion failure message when using `pytest.approx`
          on mappings with differing lengths.\n\n- [#&#8203;13773](https://redirect.github.com/pytest-dev/pytest/issues/13773):
          Fixed the static fixture closure calculation to properly consider transitive
          dependencies requested by overridden fixtures.\n\n- [#&#8203;13816](https://redirect.github.com/pytest-dev/pytest/issues/13816):
          Fixed `pytest.approx` which now returns a clearer error message when comparing
          mappings with different keys.\n\n- [#&#8203;13849](https://redirect.github.com/pytest-dev/pytest/issues/13849):
          Hidden `.pytest.ini` files are now picked up as the config file even if
          empty.\n  This was an inconsistency with non-hidden `pytest.ini`.\n\n- [#&#8203;13865](https://redirect.github.com/pytest-dev/pytest/issues/13865):
          Fixed <span class=\"title-ref\">--show-capture</span> with <span class=\"title-ref\">--tb=line</span>.\n\n-
          [#&#8203;13522](https://redirect.github.com/pytest-dev/pytest/issues/13522):
          Fixed `pytester` in subprocess mode ignored all :attr\\`pytester.plugins
          \\<pytest.Pytester.plugins>\\` except the first.\n\n  Fixed `pytester` in
          subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`.\n
          \ Now it errors instead.\n  If you are affected by this, specify the plugin
          by name, or switch the affected tests to use `pytester.runpytest_inprocess
          <pytest.Pytester.runpytest_inprocess>` explicitly instead.\n\n#### Packaging
          updates and notes for downstreams\n\n- [#&#8203;13791](https://redirect.github.com/pytest-dev/pytest/issues/13791):
          Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1`
          and `22.0.0`, respectively.\n\n#### Contributor-facing changes\n\n- [#&#8203;12244](https://redirect.github.com/pytest-dev/pytest/issues/12244):
          Fixed self-test failures when <span class=\"title-ref\">TERM=dumb</span>.\n-
          [#&#8203;12474](https://redirect.github.com/pytest-dev/pytest/issues/12474):
          Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo
          documentation.\n- [#&#8203;13621](https://redirect.github.com/pytest-dev/pytest/issues/13621):
          pytest's own testsuite now handles the `lsof` command hanging (e.g. due
          to unreachable network filesystems), with the affected selftests being skipped
          after 10 seconds.\n- [#&#8203;13638](https://redirect.github.com/pytest-dev/pytest/issues/13638):
          Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`.\n
          \ The script now uses `gh pr create` which is compatible with GitHub CLI
          v2.0+.\n- [#&#8203;13695](https://redirect.github.com/pytest-dev/pytest/issues/13695):
          Flush <span class=\"title-ref\">stdout</span> and <span class=\"title-ref\">stderr</span>
          in <span class=\"title-ref\">Pytester.run</span> to avoid truncated outputs
          in <span class=\"title-ref\">test\\_faulthandler.py::test\\_timeout</span>
          on CI -- by `ogrisel`.\n- [#&#8203;13771](https://redirect.github.com/pytest-dev/pytest/issues/13771):
          Skip <span class=\"title-ref\">test\\_do\\_not\\_collect\\_symlink\\_siblings</span>
          on Windows environments without symlink support to avoid false negatives.\n-
          [#&#8203;13841](https://redirect.github.com/pytest-dev/pytest/issues/13841):
          `tox>=4` is now required when contributing to pytest.\n- [#&#8203;13625](https://redirect.github.com/pytest-dev/pytest/issues/13625):
          Added missing docstrings to `pytest_addoption()`, `pytest_configure()`,
          and `cacheshow()` functions in `cacheprovider.py`.\n\n#### Miscellaneous
          internal changes\n\n- [#&#8203;13830](https://redirect.github.com/pytest-dev/pytest/issues/13830):
          Configuration overrides (`-o`/`--override-ini`) are now processed during
          startup rather than during `config.getini() <pytest.Config.getini>`.\n\n</details>\n\n---\n\n###
          Configuration\n\n\U0001F4C5 **Schedule**: (UTC)\n\n- Branch creation\n  -
          At any time (no schedule defined)\n- Automerge\n  - At any time (no schedule
          defined)\n\n\U0001F6A6 **Automerge**: Disabled by config. Please merge this
          manually once you are satisfied.\n\n\u267B **Rebasing**: Whenever PR becomes
          conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F515 **Ignore**:
          Close this PR and you won't be reminded about this update again.\n\n---\n\n
          - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this
          box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
          View the [repository job log](https://developer.mend.io/github/osism/ansible-collection-services).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
        change_url: https://github.com/osism/ansible-collection-services/pull/2103
        commit_id: db85d442c9f545811efe766d1b18b2a74c53c358
        patchset: db85d442c9f545811efe766d1b18b2a74c53c358
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          name: osism/ansible-collection-services
          short_name: ansible-collection-services
        src_dir: src/github.com/osism/ansible-collection-services
        topic: null
      buildset: 313274f598ab4329b6ea0756c51fe8e7
      buildset_refs:
      - branch: main
        change: '2103'
        change_message: "chore(deps): update dependency pytest to v9\n\nThis PR contains
          the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
          [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
          | `==8.4.2` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/8.4.2/9.1.0?slim=true)
          |\n\n---\n\n> [!WARNING]\n> Some dependencies could not be looked up. Check
          the [Dependency Dashboard](../issues/293) for more information.\n\n---\n\n###
          Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
          [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
          pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
          changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  If this is undesirable,
          move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
          explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
          pytest possibly collects Python modules twice, once as `pytest.Module` and
          once as a `DoctestModule` (depending on the configuration).\n  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`.\n  This
          means that both need to register the fixtures independently.\n\n##### Deprecations
          (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n  See `10819` and
          `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  See `dynamic-fixture-request-during-teardown`
          for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  These iterables get exhausted after the first iteration,\n
          \ leading to tests getting unexpectedly skipped in cases such as running
          `pytest.main()` multiple times,\n  using class-level parametrize decorators,\n
          \ or collecting tests multiple times.\n\n  See `parametrize-iterators` for
          details and suggestions.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
          <pytest.Config.getini>` to access configuration values instead.\n\n  See
          `config-inicfg` for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  Use the `node` parameter instead for fixture
          scoping. This enables more robust node-based\n  matching instead of string
          prefix matching.\n  If you've used `nodeid=None`, pass `node=session` instead.\n\n
          \ This will be removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
          The method of configuring hooks using markers, deprecated since pytest 7.2,
          is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
          details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
          The `--pastebin` option is now deprecated.\n  The same functionality is
          now available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
          for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The private `FixtureDef.has_location` attribute is now deprecated and will
          be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for
          details.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
          \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
          New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
          Added `pytest.register_fixture()` to register fixtures using an imperative
          interface.\n\n  This is an advanced function intended for use by plugins.\n\n
          \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
          <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
          during the collection phase and registers them automatically.\n  For some
          plugin usecases the declarative interface can be cumbersome or unviable,
          in which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
          Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
          [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
          Added the `assertion_text_diff_style` configuration option, allowing\n  string
          equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
          instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n##### Improvements in existing functionality\n\n-
          [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
          [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
          Improved output of `--fixtures-per-test` by excluding internal-implementation
          fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/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.\n  `func` can now also be passed as a kwarg, which
          the type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
          Improved the readability of \"DID NOT RAISE\" error messages by using the
          exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
          [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
          Added test coverage for compiled regex patterns in `pytest.raises` match
          parameter.\n\n- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
          <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow
          using it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
          Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
          decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
          in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
          Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
          [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
          Improved assertion failure explanations for equality comparisons between
          mapping objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The order in which fixture definitions overriding each other are resolved
          is now determined first by their *visibility* in the collection tree rather
          than by the order in which they are registered.\n\n  A fixture defined for
          a more specific node (e.g. a module or an item) now always takes precedence
          over one with the same name defined for a more general node (e.g. the session),
          even when the more general one was registered later.\n  Fixtures with non-comparable
          visibility or the same visibility keep the existing behavior of \"last registered
          wins\".\n  This change is supposed to only affect plugins which register
          multiple fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
          Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          Improved argparse program name to show `pytest`, `python -m pytest`, or
          `pytest.main()` based on how pytest was invoked, making help and error messages
          clearer.\n\n- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
          Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
          `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
          this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
          pytest issues a helpful warning and continues collecting the module normally.\n\n#####
          Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
          Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
          meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
          [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
          Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
          [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
          Fixed function-scoped fixture values being kept alive after a test was interrupted
          by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be
          released more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
          Fixed `capteesys` producing doubled output when used with `--capture=no`
          (`-s`).\n\n- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
          Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
          the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
          Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
          being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
          Fixed autouse fixtures defined inside a `unittest.TestCase` class running
          even when the class is decorated with `unittest.skip` or `unittest.skipIf`
          -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
          `unittest.SkipTest` is no longer considered an interactive exception, i.e.
          `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
          Fixed subtests running with `pytest-xdist` when their contexts contain objects
          that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
          [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Fixed conftest.py fixture scoping when `testpaths` points outside of the
          `rootdir <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files
          would incorrectly leak to sibling directories\n  when using a relative `testpaths`
          like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
          <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
          [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
          Display dictionary differences in assertion failures using the original
          key insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
          fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
          methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
          An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
          from being torn down, causing additional errors in the following tests.\n\n-
          [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
          Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
          entry on the undo stack when the underlying `setattr()` call fails (e.g.
          on immutable targets), causing an `AttributeError` crash during teardown.\n\n-
          [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
          Fixed `-v` hint in `pytest.raises` match diff not working because assertion
          verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
          Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
          <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
          Fixed direct parametrization causing the static fixture closure (as reflected
          in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit
          fixtures that are requested transitively from overridden fixtures.\n\n-
          [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
          Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
          before pytest tears down the warning filters installed for the session.
          Previously the collection ran from a cleanup callback whose order relative
          to other plugins' cleanups was not guaranteed, so an active `error` filter
          could be removed before the exception surfaced and a late resource leak
          would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
          now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
          [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
          Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
          when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
          [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
          Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
          [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
          Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
          the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
          [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
          Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
          detection, causing the regex diff display to be shown in some instances
          when the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
          Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
          specified through `addopts` were silently ignored.\n\n  Note that when targeting
          pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
          `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
          Fixed `pytest.approx` not recognizing types with `__array_interface__` as
          numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
          Fixed a regression where `-k` and `-m` expressions containing both backslash
          characters in identifiers and string literal arguments would incorrectly
          raise a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
          Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
          plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
          [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
          Fixed `Code.getargs()` incorrectly including local variable names in the
          returned argument tuple for functions with `*args` and/or `**kwargs`. The
          method was using `co_flags` bitmask values (`4` and `8`) directly as counts
          instead of converting them to `1` via `bool()`, and was not accounting for
          `co_kwonlyargcount` when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
          Logging capture now works for non-propagating loggers.\n  Previously only
          logs which reached the root logger were captured.\n  This includes `caplog`
          and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
          Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
          now always matches the number of `<testcase>` elements in the file. In some
          cases (test passes but fails during teardown) the `tests` attribute would
          report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
          `pytest_fixture_post_finalizer` is no longer called extra times for the
          same fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
          Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
          single-element tuple values when using a string argnames with a trailing
          comma (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves
          like the tuple form `(\"arg\",)`, treating argvalues as a list of tuples
          to unpack.\n\n##### Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
          Document safer alternatives and scope guidance for monkeypatching standard
          library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
          Document that `@pytest.hookimpl(specname=...)` only works for function names
          starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
          Document that doctests do not support parametrized fixtures, including parametrized
          autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
          Clarified how the `request` fixture provides indirect parametrization values
          via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
          Clarified in the documentation that hook implementations defined in `conftest.py`
          files are not available to other plugins during their `pytest_addoption()`
          execution, as conftest files are discovered and loaded after builtin and
          third-party plugins have been initialized. However, initial conftest files
          themselves can implement `pytest_addoption()` to add their own command-line
          options.\n- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
          Clarified how subtest progress markers are shown in the documentation.\n-
          [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
          The `ini options ref` section of the API Reference now specified the type
          and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
          Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
          plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
          The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
          Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
          at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
          Pointing at a tag keeps the example in sync with the version users actually
          install, while remaining stable when the project's main branch moves on.\n\n#####
          Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
          Improved the recursion traceback test to exercise all requested traceback
          styles.\n\n### [`v9.0.3`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.3)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.2...9.0.3)\n\n###
          pytest 9.0.3 (2026-04-07)\n\n#### Bug fixes\n\n- [#&#8203;12444](https://redirect.github.com/pytest-dev/pytest/issues/12444):
          Fixed `pytest.approx` which now correctly takes into account `~collections.abc.Mapping`
          keys order to compare them.\n\n- [#&#8203;13634](https://redirect.github.com/pytest-dev/pytest/issues/13634):
          Blocking a `conftest.py` file using the `-p no:` option is now explicitly
          disallowed.\n\n  Previously this resulted in an internal assertion failure
          during plugin loading.\n\n  Pytest now raises a clear `UsageError` explaining
          that conftest files are not plugins and cannot be disabled via `-p`.\n\n-
          [#&#8203;13734](https://redirect.github.com/pytest-dev/pytest/issues/13734):
          Fixed crash when a test raises an exceptiongroup with `__tracebackhide__
          = True`.\n\n- [#&#8203;14195](https://redirect.github.com/pytest-dev/pytest/issues/14195):
          Fixed an issue where non-string messages passed to <span class=\"title-ref\">unittest.TestCase.subTest()</span>
          were not printed.\n\n- [#&#8203;14343](https://redirect.github.com/pytest-dev/pytest/issues/14343):
          Fixed use of insecure temporary directory (CVE-2025-71176).\n\n#### Improved
          documentation\n\n- [#&#8203;13388](https://redirect.github.com/pytest-dev/pytest/issues/13388):
          Clarified documentation for `-p` vs `PYTEST_PLUGINS` plugin loading and
          fixed an incorrect `-p` example.\n- [#&#8203;13731](https://redirect.github.com/pytest-dev/pytest/issues/13731):
          Clarified that capture fixtures (e.g. `capsys` and `capfd`) take precedence
          over the `-s` / `--capture=no` command-line options in `Accessing captured
          output from a test function <accessing-captured-output>`.\n- [#&#8203;14088](https://redirect.github.com/pytest-dev/pytest/issues/14088):
          Clarified that the default `pytest_collection` hook sets `session.items`
          before it calls `pytest_collection_finish`, not after.\n- [#&#8203;14255](https://redirect.github.com/pytest-dev/pytest/issues/14255):
          TOML integer log levels must be quoted: Updating reference documentation.\n\n####
          Contributor-facing changes\n\n- [#&#8203;12689](https://redirect.github.com/pytest-dev/pytest/issues/12689):
          The test reports are now published to Codecov from GitHub Actions.\n  The
          test statistics is visible [on the web interface](https://app.codecov.io/gh/pytest-dev/pytest/tests).\n\n
          \ \\-- by `aleguy02`\n\n### [`v9.0.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.2)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.1...9.0.2)\n\n###
          pytest 9.0.2 (2025-12-06)\n\n#### Bug fixes\n\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
          The terminal progress feature added in pytest 9.0.0 has been disabled by
          default, except on Windows, due to compatibility issues with some terminal
          emulators.\n\n  You may enable it again by passing `-p terminalprogress`.
          We may enable it by default again once compatibility improves in the future.\n\n
          \ Additionally, when the environment variable `TERM` is `dumb`, the escape
          codes are no longer emitted, even if the plugin is enabled.\n\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
          Fixed the TOML type of the `tmp_path_retention_count` settings in the API
          reference from number to string.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute was changed in a breaking manner in
          pytest 9.0.0.\n  Due to its usage in the ecosystem, it is now restored to
          working order using a compatibility shim.\n  It will be deprecated in pytest
          9.1 and removed in pytest 10.\n\n- [#&#8203;13965](https://redirect.github.com/pytest-dev/pytest/issues/13965):
          Fixed quadratic-time behavior when handling `unittest` subtests in Python
          3.10.\n\n#### Improved documentation\n\n- [#&#8203;4492](https://redirect.github.com/pytest-dev/pytest/issues/4492):
          The API Reference now contains cross-reference-able documentation of `pytest's
          command-line flags <command-line-flags>`.\n\n### [`v9.0.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.1)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.0...9.0.1)\n\n###
          pytest 9.0.1 (2025-11-12)\n\n#### Bug fixes\n\n- [#&#8203;13895](https://redirect.github.com/pytest-dev/pytest/issues/13895):
          Restore support for skipping tests via `raise unittest.SkipTest`.\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
          The terminal progress plugin added in pytest 9.0 is now automatically disabled
          when iTerm2 is detected, it generated desktop notifications instead of the
          desired functionality.\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
          Fixed the TOML type of the verbosity settings in the API reference from
          number to string.\n- [#&#8203;13910](https://redirect.github.com/pytest-dev/pytest/issues/13910):
          Fixed <span class=\"title-ref\">UserWarning: Do not expect file\\_or\\_dir</span>
          on some earlier Python 3.12 and 3.13 point versions.\n\n#### Packaging updates
          and notes for downstreams\n\n- [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
          The tox configuration has been adjusted to make sure the desired\n  version
          string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
          environment\n  variable as a part of the release process -- by `webknjaz`.\n\n####
          Contributor-facing changes\n\n- [#&#8203;13891](https://redirect.github.com/pytest-dev/pytest/issues/13891),
          [#&#8203;13942](https://redirect.github.com/pytest-dev/pytest/issues/13942):
          The CI/CD part of the release automation is now capable of\n  creating GitHub
          Releases without having a Git checkout on\n  disk -- by `bluetech` and `webknjaz`.\n-
          [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
          The tox configuration has been adjusted to make sure the desired\n  version
          string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
          environment\n  variable as a part of the release process -- by `webknjaz`.\n\n###
          [`v9.0.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/8.4.2...9.0.0)\n\n###
          pytest 9.0.0 (2025-11-05)\n\n#### New features\n\n- [#&#8203;1367](https://redirect.github.com/pytest-dev/pytest/issues/1367):
          **Support for subtests** has been added.\n\n  `subtests <subtests>` are
          an alternative to parametrization, useful in situations where the parametrization
          values are not all known at collection time.\n\n  Example:\n\n  ```python\n
          \ def contains_docstring(p: Path) -> bool:\n      \"\"\"Return True if the
          given Python file contains a top-level docstring.\"\"\"\n      ...\n\n  def
          test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:\n      for
          path in Path.cwd().glob(\"*.py\"):\n          with subtests.test(path=str(path)):\n
          \             assert contains_docstring(path)\n  ```\n\n  Each assert failure
          or error is caught by the context manager and reported individually, giving
          a clear picture of all files that are missing a docstring.\n\n  In addition,
          `unittest.TestCase.subTest` is now also supported.\n\n  This feature was
          originally implemented as a separate plugin in [pytest-subtests](https://redirect.github.com/pytest-dev/pytest-subtests),
          but since then has been merged into the core.\n\n  > \\[!NOTE]\n  > This
          feature is experimental and will likely evolve in future releases. By that
          we mean that we might change how subtests are reported on failure, but the
          functionality and how to use it are stable.\n\n- [#&#8203;13743](https://redirect.github.com/pytest-dev/pytest/issues/13743):
          Added support for **native TOML configuration files**.\n\n  While pytest,
          since version 6, supports configuration in `pyproject.toml` files under
          `[tool.pytest.ini_options]`,\n  it does so in an \"INI compatibility mode\",
          where all configuration values are treated as strings or list of strings.\n
          \ Now, pytest supports the native TOML data model.\n\n  In `pyproject.toml`,
          the native TOML configuration is under the `[tool.pytest]` table.\n\n  ```toml\n
          \ # pyproject.toml\n  [tool.pytest]\n  minversion = \"9.0\"\n  addopts =
          [\"-ra\", \"-q\"]\n  testpaths = [\n      \"tests\",\n      \"integration\",\n
          \ ]\n  ```\n\n  The `[tool.pytest.ini_options]` table remains supported,
          but both tables cannot be used at the same time.\n\n  If you prefer to use
          a separate configuration file, or don't use `pyproject.toml`, you can use
          `pytest.toml` or `.pytest.toml`:\n\n  ```toml\n  # pytest.toml or .pytest.toml\n
          \ [pytest]\n  minversion = \"9.0\"\n  addopts = [\"-ra\", \"-q\"]\n  testpaths
          = [\n      \"tests\",\n      \"integration\",\n  ]\n  ```\n\n  The documentation
          now (sometimes) shows configuration snippets in both TOML and INI formats,
          in a tabbed interface.\n\n  See `config file formats` for full details.\n\n-
          [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
          Added a **\"strict mode\"** enabled by the `strict` configuration option.\n\n
          \ When set to `true`, the `strict` option currently enables\n\n  - `strict_config`\n
          \ - `strict_markers`\n  - `strict_parametrization_ids`\n  - `strict_xfail`\n\n
          \ The individual strictness options can be explicitly set to override the
          global `strict` setting.\n\n  The previously-deprecated `--strict` command-line
          flag now enables strict mode.\n\n  If pytest adds new strictness options
          in the future, they will also be enabled in strict mode.\n  Therefore, you
          should only enable strict mode if you use a pinned/locked version of pytest,\n
          \ or if you want to proactively adopt new strictness options as they are
          added.\n\n  See `strict mode` for more details.\n\n- [#&#8203;13737](https://redirect.github.com/pytest-dev/pytest/issues/13737):
          Added the `strict_parametrization_ids` configuration option.\n\n  When set,
          pytest emits an error if it detects non-unique parameter set IDs,\n  rather
          than automatically making the IDs unique by adding <span class=\"title-ref\">0</span>,
          <span class=\"title-ref\">1</span>, ... to them.\n  This can be particularly
          useful for catching unintended duplicates.\n\n- [#&#8203;13072](https://redirect.github.com/pytest-dev/pytest/issues/13072):
          Added support for displaying test session **progress in the terminal tab**
          using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC)
          ANSI sequence.\n  When pytest runs in a supported terminal emulator like
          ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,\n  you'll
          see the progress in the terminal tab or window,\n  allowing you to monitor
          pytest's progress at a glance.\n\n  This feature is automatically enabled
          when running in a TTY. It is implemented as an internal plugin. If needed,
          it can be disabled as follows:\n\n  - On a user level, using `-p no:terminalprogress`
          on the command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`.\n
          \ - On a project configuration level, using `addopts = \"-p no:terminalprogress\"`.\n\n-
          [#&#8203;478](https://redirect.github.com/pytest-dev/pytest/issues/478):
          Support PEP420 (implicit namespace packages) as <span class=\"title-ref\">--pyargs</span>
          target when `consider_namespace_packages` is <span class=\"title-ref\">true</span>
          in the config.\n\n  Previously, this option only impacted package imports,
          now it also impacts tests discovery.\n\n- [#&#8203;13678](https://redirect.github.com/pytest-dev/pytest/issues/13678):
          Added a new `faulthandler_exit_on_timeout` configuration option set to \"false\"
          by default to let <span class=\"title-ref\">faulthandler</span> interrupt
          the <span class=\"title-ref\">pytest</span> process after a timeout in case
          of deadlock.\n\n  Previously, a <span class=\"title-ref\">faulthandler</span>
          timeout would only dump the traceback of all threads to stderr, but would
          not interrupt the <span class=\"title-ref\">pytest</span> process.\n\n  \\--
          by `ogrisel`.\n\n- [#&#8203;13829](https://redirect.github.com/pytest-dev/pytest/issues/13829):
          Added support for configuration option aliases via the `aliases` parameter
          in `Parser.addini() <pytest.Parser.addini>`.\n\n  Plugins can now register
          alternative names for configuration options,\n  allowing for more flexibility
          in configuration naming and supporting backward compatibility when renaming
          options.\n  The canonical name always takes precedence if both the canonical
          name and an alias are specified in the configuration file.\n\n#### Improvements
          in existing functionality\n\n- [#&#8203;13330](https://redirect.github.com/pytest-dev/pytest/issues/13330):
          Having pytest configuration spread over more than one file (for example
          having both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]`
          table) will now print a warning to make it clearer to the user that only
          one of them is actually used.\n\n  \\-- by `sgaist`\n\n- [#&#8203;13574](https://redirect.github.com/pytest-dev/pytest/issues/13574):
          The single argument `--version` no longer loads the entire plugin infrastructure,
          making it faster and more reliable when displaying only the pytest version.\n\n
          \ Passing `--version` twice (e.g., `pytest --version --version`) retains
          the original behavior, showing both the pytest version and plugin information.\n\n
          \ > \\[!NOTE]\n  > Since `--version` is now processed early, it only takes
          effect when passed directly via the command line. It will not work if set
          through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`.\n\n- [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
          Added `strict_xfail` as an alias to the `xfail_strict` option,\n  `strict_config`
          as an alias to the `--strict-config` flag,\n  and `strict_markers` as an
          alias to the `--strict-markers` flag.\n  This makes all strictness options
          consistently have configuration options with the prefix `strict_`.\n\n-
          [#&#8203;13700](https://redirect.github.com/pytest-dev/pytest/issues/13700):
          <span class=\"title-ref\">--junitxml</span> no longer prints the <span class=\"title-ref\">generated
          xml file</span> summary at the end of the pytest session when <span class=\"title-ref\">--quiet</span>
          is given.\n\n- [#&#8203;13732](https://redirect.github.com/pytest-dev/pytest/issues/13732):
          Previously, when filtering warnings, pytest would fail if the filter referenced
          a class that could not be imported. Now, this only outputs a message indicating
          the problem.\n\n- [#&#8203;13859](https://redirect.github.com/pytest-dev/pytest/issues/13859):
          Clarify the error message for <span class=\"title-ref\">pytest.raises()</span>
          when a regex <span class=\"title-ref\">match</span> fails.\n\n- [#&#8203;13861](https://redirect.github.com/pytest-dev/pytest/issues/13861):
          Better sentence structure in a test's expected error message. Previously,
          the error message would be \"expected exception must be \\<expected>, but
          got \\<actual>\". Now, it is \"Expected \\<expected>, but got \\<actual>\".\n\n####
          Removals and backward incompatible breaking changes\n\n- [#&#8203;12083](https://redirect.github.com/pytest-dev/pytest/issues/12083):
          Fixed a bug where an invocation such as <span class=\"title-ref\">pytest
          a/ a/b</span> would cause only tests from <span class=\"title-ref\">a/b</span>
          to run, and not other tests under <span class=\"title-ref\">a/</span>.\n\n
          \ The fix entails a few breaking changes to how such overlapping arguments
          and duplicates are handled:\n\n  1. <span class=\"title-ref\">pytest a/b
          a/</span> or <span class=\"title-ref\">pytest a/ a/b</span> are equivalent
          to <span class=\"title-ref\">pytest a</span>; if an argument overlaps another
          arguments, only the prefix remains.\n  2. <span class=\"title-ref\">pytest
          x.py x.py</span> is equivalent to <span class=\"title-ref\">pytest x.py</span>;
          previously such an invocation was taken as an explicit request to run the
          tests from the file twice.\n\n  If you rely on these behaviors, consider
          using `--keep-duplicates <duplicate-paths>`, which retains its existing
          behavior (including the bug).\n\n- [#&#8203;13719](https://redirect.github.com/pytest-dev/pytest/issues/13719):
          Support for Python 3.9 is dropped following its end of life.\n\n- [#&#8203;13766](https://redirect.github.com/pytest-dev/pytest/issues/13766):
          Previously, pytest would assume it was running in a CI/CD environment if
          either of the environment variables <span class=\"title-ref\">$CI</span>
          or <span class=\"title-ref\">$BUILD\\_NUMBER</span> was defined;\n  now,
          CI mode is only activated if at least one of those variables is defined
          and set to a *non-empty* value.\n\n- [#&#8203;13779](https://redirect.github.com/pytest-dev/pytest/issues/13779):
          **PytestRemovedIn9Warning deprecation warnings are now errors by default.**\n\n
          \ Following our plan to remove deprecated features with as little disruption
          as\n  possible, all warnings of type `PytestRemovedIn9Warning` now generate
          errors\n  instead of warning messages by default.\n\n  **The affected features
          will be effectively removed in pytest 9.1**, so please consult the\n  `deprecations`
          section in the docs for directions on how to update existing code.\n\n  In
          the pytest `9.0.X` series, it is possible to change the errors back into
          warnings as a\n  stopgap measure by adding this to your `pytest.ini` file:\n\n
          \ ```ini\n  [pytest]\n  filterwarnings =\n      ignore::pytest.PytestRemovedIn9Warning\n
          \ ```\n\n  But this will stop working when pytest `9.1` is released.\n\n
          \ **If you have concerns** about the removal of a specific feature, please
          add a\n  comment to `13779`.\n\n#### Deprecations (removal in next major
          release)\n\n- [#&#8203;13807](https://redirect.github.com/pytest-dev/pytest/issues/13807):
          `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now
          issues a deprecation warning when the prepended path contains legacy namespace
          packages (those using `pkg_resources.declare_namespace()`).\n  Users should
          migrate to native namespace packages (`420`).\n  See `monkeypatch-fixup-namespace-packages`
          for details.\n\n#### Bug fixes\n\n- [#&#8203;13445](https://redirect.github.com/pytest-dev/pytest/issues/13445):
          Made the type annotations of `pytest.skip` and friends more spec-complaint
          to have them work across more type checkers.\n\n- [#&#8203;13537](https://redirect.github.com/pytest-dev/pytest/issues/13537):
          Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in
          teardown was not handled correctly and showed as error.\n\n- [#&#8203;13598](https://redirect.github.com/pytest-dev/pytest/issues/13598):
          Fixed possible collection confusion on Windows when short paths and symlinks
          are involved.\n\n- [#&#8203;13716](https://redirect.github.com/pytest-dev/pytest/issues/13716):
          Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file
          cannot be parametrized) was silently treated as `pytest x.py`. This is now
          a usage error.\n\n- [#&#8203;13722](https://redirect.github.com/pytest-dev/pytest/issues/13722):
          Fixed a misleading assertion failure message when using `pytest.approx`
          on mappings with differing lengths.\n\n- [#&#8203;13773](https://redirect.github.com/pytest-dev/pytest/issues/13773):
          Fixed the static fixture closure calculation to properly consider transitive
          dependencies requested by overridden fixtures.\n\n- [#&#8203;13816](https://redirect.github.com/pytest-dev/pytest/issues/13816):
          Fixed `pytest.approx` which now returns a clearer error message when comparing
          mappings with different keys.\n\n- [#&#8203;13849](https://redirect.github.com/pytest-dev/pytest/issues/13849):
          Hidden `.pytest.ini` files are now picked up as the config file even if
          empty.\n  This was an inconsistency with non-hidden `pytest.ini`.\n\n- [#&#8203;13865](https://redirect.github.com/pytest-dev/pytest/issues/13865):
          Fixed <span class=\"title-ref\">--show-capture</span> with <span class=\"title-ref\">--tb=line</span>.\n\n-
          [#&#8203;13522](https://redirect.github.com/pytest-dev/pytest/issues/13522):
          Fixed `pytester` in subprocess mode ignored all :attr\\`pytester.plugins
          \\<pytest.Pytester.plugins>\\` except the first.\n\n  Fixed `pytester` in
          subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`.\n
          \ Now it errors instead.\n  If you are affected by this, specify the plugin
          by name, or switch the affected tests to use `pytester.runpytest_inprocess
          <pytest.Pytester.runpytest_inprocess>` explicitly instead.\n\n#### Packaging
          updates and notes for downstreams\n\n- [#&#8203;13791](https://redirect.github.com/pytest-dev/pytest/issues/13791):
          Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1`
          and `22.0.0`, respectively.\n\n#### Contributor-facing changes\n\n- [#&#8203;12244](https://redirect.github.com/pytest-dev/pytest/issues/12244):
          Fixed self-test failures when <span class=\"title-ref\">TERM=dumb</span>.\n-
          [#&#8203;12474](https://redirect.github.com/pytest-dev/pytest/issues/12474):
          Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo
          documentation.\n- [#&#8203;13621](https://redirect.github.com/pytest-dev/pytest/issues/13621):
          pytest's own testsuite now handles the `lsof` command hanging (e.g. due
          to unreachable network filesystems), with the affected selftests being skipped
          after 10 seconds.\n- [#&#8203;13638](https://redirect.github.com/pytest-dev/pytest/issues/13638):
          Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`.\n
          \ The script now uses `gh pr create` which is compatible with GitHub CLI
          v2.0+.\n- [#&#8203;13695](https://redirect.github.com/pytest-dev/pytest/issues/13695):
          Flush <span class=\"title-ref\">stdout</span> and <span class=\"title-ref\">stderr</span>
          in <span class=\"title-ref\">Pytester.run</span> to avoid truncated outputs
          in <span class=\"title-ref\">test\\_faulthandler.py::test\\_timeout</span>
          on CI -- by `ogrisel`.\n- [#&#8203;13771](https://redirect.github.com/pytest-dev/pytest/issues/13771):
          Skip <span class=\"title-ref\">test\\_do\\_not\\_collect\\_symlink\\_siblings</span>
          on Windows environments without symlink support to avoid false negatives.\n-
          [#&#8203;13841](https://redirect.github.com/pytest-dev/pytest/issues/13841):
          `tox>=4` is now required when contributing to pytest.\n- [#&#8203;13625](https://redirect.github.com/pytest-dev/pytest/issues/13625):
          Added missing docstrings to `pytest_addoption()`, `pytest_configure()`,
          and `cacheshow()` functions in `cacheprovider.py`.\n\n#### Miscellaneous
          internal changes\n\n- [#&#8203;13830](https://redirect.github.com/pytest-dev/pytest/issues/13830):
          Configuration overrides (`-o`/`--override-ini`) are now processed during
          startup rather than during `config.getini() <pytest.Config.getini>`.\n\n</details>\n\n---\n\n###
          Configuration\n\n\U0001F4C5 **Schedule**: (UTC)\n\n- Branch creation\n  -
          At any time (no schedule defined)\n- Automerge\n  - At any time (no schedule
          defined)\n\n\U0001F6A6 **Automerge**: Disabled by config. Please merge this
          manually once you are satisfied.\n\n\u267B **Rebasing**: Whenever PR becomes
          conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F515 **Ignore**:
          Close this PR and you won't be reminded about this update again.\n\n---\n\n
          - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this
          box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
          View the [repository job log](https://developer.mend.io/github/osism/ansible-collection-services).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
        change_url: https://github.com/osism/ansible-collection-services/pull/2103
        commit_id: db85d442c9f545811efe766d1b18b2a74c53c358
        patchset: db85d442c9f545811efe766d1b18b2a74c53c358
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          name: osism/ansible-collection-services
          short_name: ansible-collection-services
        src_dir: src/github.com/osism/ansible-collection-services
        topic: null
      change: '2103'
      change_message: "chore(deps): update dependency pytest to v9\n\nThis PR contains
        the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
        | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
        [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
        | `==8.4.2` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/8.4.2/9.1.0?slim=true)
        |\n\n---\n\n> [!WARNING]\n> Some dependencies could not be looked up. Check
        the [Dependency Dashboard](../issues/293) for more information.\n\n---\n\n###
        Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
        [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
        Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
        pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
        changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  If this is undesirable,
        move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
        explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
        pytest possibly collects Python modules twice, once as `pytest.Module` and
        once as a `DoctestModule` (depending on the configuration).\n  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`.\n  This means
        that both need to register the fixtures independently.\n\n##### Deprecations
        (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n  See `10819` and `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  See `dynamic-fixture-request-during-teardown`
        for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  These iterables get exhausted after the first iteration,\n
        \ leading to tests getting unexpectedly skipped in cases such as running `pytest.main()`
        multiple times,\n  using class-level parametrize decorators,\n  or collecting
        tests multiple times.\n\n  See `parametrize-iterators` for details and suggestions.\n\n-
        [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
        The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
        <pytest.Config.getini>` to access configuration values instead.\n\n  See `config-inicfg`
        for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  Use the `node` parameter instead for fixture scoping. This enables
        more robust node-based\n  matching instead of string prefix matching.\n  If
        you've used `nodeid=None`, pass `node=session` instead.\n\n  This will be
        removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
        The method of configuring hooks using markers, deprecated since pytest 7.2,
        is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
        details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
        The `--pastebin` option is now deprecated.\n  The same functionality is now
        available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
        for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
        The private `FixtureDef.has_location` attribute is now deprecated and will
        be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for details.\n\n-
        [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
        `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
        \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
        New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
        Added `pytest.register_fixture()` to register fixtures using an imperative
        interface.\n\n  This is an advanced function intended for use by plugins.\n\n
        \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
        <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
        during the collection phase and registers them automatically.\n  For some
        plugin usecases the declarative interface can be cumbersome or unviable, in
        which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
        Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
        [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
        Added the `assertion_text_diff_style` configuration option, allowing\n  string
        equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
        instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n##### Improvements in existing functionality\n\n-
        [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
        [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
        Improved output of `--fixtures-per-test` by excluding internal-implementation
        fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/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.\n  `func` can now also be passed as a kwarg, which the
        type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
        Improved the readability of \"DID NOT RAISE\" error messages by using the
        exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
        [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
        Added test coverage for compiled regex patterns in `pytest.raises` match parameter.\n\n-
        [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
        <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow using
        it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
        Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
        decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
        in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
        Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
        [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
        Improved assertion failure explanations for equality comparisons between mapping
        objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
        The order in which fixture definitions overriding each other are resolved
        is now determined first by their *visibility* in the collection tree rather
        than by the order in which they are registered.\n\n  A fixture defined for
        a more specific node (e.g. a module or an item) now always takes precedence
        over one with the same name defined for a more general node (e.g. the session),
        even when the more general one was registered later.\n  Fixtures with non-comparable
        visibility or the same visibility keep the existing behavior of \"last registered
        wins\".\n  This change is supposed to only affect plugins which register multiple
        fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
        Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
        Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()`
        based on how pytest was invoked, making help and error messages clearer.\n\n-
        [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
        Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
        `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
        this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
        pytest issues a helpful warning and continues collecting the module normally.\n\n#####
        Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
        Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
        meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
        [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
        Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
        [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
        Fixed function-scoped fixture values being kept alive after a test was interrupted
        by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be released
        more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
        Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`).\n\n-
        [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
        Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
        the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
        Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
        being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
        Fixed autouse fixtures defined inside a `unittest.TestCase` class running
        even when the class is decorated with `unittest.skip` or `unittest.skipIf`
        -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
        `unittest.SkipTest` is no longer considered an interactive exception, i.e.
        `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
        Fixed subtests running with `pytest-xdist` when their contexts contain objects
        that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
        [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
        Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir
        <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files would
        incorrectly leak to sibling directories\n  when using a relative `testpaths`
        like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
        <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
        [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
        Display dictionary differences in assertion failures using the original key
        insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
        fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
        methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
        An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
        from being torn down, causing additional errors in the following tests.\n\n-
        [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
        Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
        entry on the undo stack when the underlying `setattr()` call fails (e.g. on
        immutable targets), causing an `AttributeError` crash during teardown.\n\n-
        [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
        Fixed `-v` hint in `pytest.raises` match diff not working because assertion
        verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
        Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
        <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
        Fixed direct parametrization causing the static fixture closure (as reflected
        in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures
        that are requested transitively from overridden fixtures.\n\n- [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
        Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
        before pytest tears down the warning filters installed for the session. Previously
        the collection ran from a cleanup callback whose order relative to other plugins'
        cleanups was not guaranteed, so an active `error` filter could be removed
        before the exception surfaced and a late resource leak would pass silently.
        A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
        now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
        [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
        Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
        when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
        [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
        Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
        [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
        Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
        the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
        [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
        Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
        detection, causing the regex diff display to be shown in some instances when
        the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
        Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
        specified through `addopts` were silently ignored.\n\n  Note that when targeting
        pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
        `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
        Fixed `pytest.approx` not recognizing types with `__array_interface__` as
        numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
        Fixed a regression where `-k` and `-m` expressions containing both backslash
        characters in identifiers and string literal arguments would incorrectly raise
        a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
        Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
        plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
        [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
        Fixed `Code.getargs()` incorrectly including local variable names in the returned
        argument tuple for functions with `*args` and/or `**kwargs`. The method was
        using `co_flags` bitmask values (`4` and `8`) directly as counts instead of
        converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount`
        when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
        Logging capture now works for non-propagating loggers.\n  Previously only
        logs which reached the root logger were captured.\n  This includes `caplog`
        and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
        Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
        now always matches the number of `<testcase>` elements in the file. In some
        cases (test passes but fails during teardown) the `tests` attribute would
        report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
        `pytest_fixture_post_finalizer` is no longer called extra times for the same
        fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
        Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
        single-element tuple values when using a string argnames with a trailing comma
        (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves like
        the tuple form `(\"arg\",)`, treating argvalues as a list of tuples to unpack.\n\n#####
        Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
        Document safer alternatives and scope guidance for monkeypatching standard
        library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
        Document that `@pytest.hookimpl(specname=...)` only works for function names
        starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
        Document that doctests do not support parametrized fixtures, including parametrized
        autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
        Clarified how the `request` fixture provides indirect parametrization values
        via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
        Clarified in the documentation that hook implementations defined in `conftest.py`
        files are not available to other plugins during their `pytest_addoption()`
        execution, as conftest files are discovered and loaded after builtin and third-party
        plugins have been initialized. However, initial conftest files themselves
        can implement `pytest_addoption()` to add their own command-line options.\n-
        [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
        Clarified how subtest progress markers are shown in the documentation.\n-
        [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
        The `ini options ref` section of the API Reference now specified the type
        and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
        Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
        plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
        The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
        Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
        at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
        Pointing at a tag keeps the example in sync with the version users actually
        install, while remaining stable when the project's main branch moves on.\n\n#####
        Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
        Improved the recursion traceback test to exercise all requested traceback
        styles.\n\n### [`v9.0.3`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.3)\n\n[Compare
        Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.2...9.0.3)\n\n###
        pytest 9.0.3 (2026-04-07)\n\n#### Bug fixes\n\n- [#&#8203;12444](https://redirect.github.com/pytest-dev/pytest/issues/12444):
        Fixed `pytest.approx` which now correctly takes into account `~collections.abc.Mapping`
        keys order to compare them.\n\n- [#&#8203;13634](https://redirect.github.com/pytest-dev/pytest/issues/13634):
        Blocking a `conftest.py` file using the `-p no:` option is now explicitly
        disallowed.\n\n  Previously this resulted in an internal assertion failure
        during plugin loading.\n\n  Pytest now raises a clear `UsageError` explaining
        that conftest files are not plugins and cannot be disabled via `-p`.\n\n-
        [#&#8203;13734](https://redirect.github.com/pytest-dev/pytest/issues/13734):
        Fixed crash when a test raises an exceptiongroup with `__tracebackhide__ =
        True`.\n\n- [#&#8203;14195](https://redirect.github.com/pytest-dev/pytest/issues/14195):
        Fixed an issue where non-string messages passed to <span class=\"title-ref\">unittest.TestCase.subTest()</span>
        were not printed.\n\n- [#&#8203;14343](https://redirect.github.com/pytest-dev/pytest/issues/14343):
        Fixed use of insecure temporary directory (CVE-2025-71176).\n\n#### Improved
        documentation\n\n- [#&#8203;13388](https://redirect.github.com/pytest-dev/pytest/issues/13388):
        Clarified documentation for `-p` vs `PYTEST_PLUGINS` plugin loading and fixed
        an incorrect `-p` example.\n- [#&#8203;13731](https://redirect.github.com/pytest-dev/pytest/issues/13731):
        Clarified that capture fixtures (e.g. `capsys` and `capfd`) take precedence
        over the `-s` / `--capture=no` command-line options in `Accessing captured
        output from a test function <accessing-captured-output>`.\n- [#&#8203;14088](https://redirect.github.com/pytest-dev/pytest/issues/14088):
        Clarified that the default `pytest_collection` hook sets `session.items` before
        it calls `pytest_collection_finish`, not after.\n- [#&#8203;14255](https://redirect.github.com/pytest-dev/pytest/issues/14255):
        TOML integer log levels must be quoted: Updating reference documentation.\n\n####
        Contributor-facing changes\n\n- [#&#8203;12689](https://redirect.github.com/pytest-dev/pytest/issues/12689):
        The test reports are now published to Codecov from GitHub Actions.\n  The
        test statistics is visible [on the web interface](https://app.codecov.io/gh/pytest-dev/pytest/tests).\n\n
        \ \\-- by `aleguy02`\n\n### [`v9.0.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.2)\n\n[Compare
        Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.1...9.0.2)\n\n###
        pytest 9.0.2 (2025-12-06)\n\n#### Bug fixes\n\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
        The terminal progress feature added in pytest 9.0.0 has been disabled by default,
        except on Windows, due to compatibility issues with some terminal emulators.\n\n
        \ You may enable it again by passing `-p terminalprogress`. We may enable
        it by default again once compatibility improves in the future.\n\n  Additionally,
        when the environment variable `TERM` is `dumb`, the escape codes are no longer
        emitted, even if the plugin is enabled.\n\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
        Fixed the TOML type of the `tmp_path_retention_count` settings in the API
        reference from number to string.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
        The private `config.inicfg` attribute was changed in a breaking manner in
        pytest 9.0.0.\n  Due to its usage in the ecosystem, it is now restored to
        working order using a compatibility shim.\n  It will be deprecated in pytest
        9.1 and removed in pytest 10.\n\n- [#&#8203;13965](https://redirect.github.com/pytest-dev/pytest/issues/13965):
        Fixed quadratic-time behavior when handling `unittest` subtests in Python
        3.10.\n\n#### Improved documentation\n\n- [#&#8203;4492](https://redirect.github.com/pytest-dev/pytest/issues/4492):
        The API Reference now contains cross-reference-able documentation of `pytest's
        command-line flags <command-line-flags>`.\n\n### [`v9.0.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.1)\n\n[Compare
        Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.0...9.0.1)\n\n###
        pytest 9.0.1 (2025-11-12)\n\n#### Bug fixes\n\n- [#&#8203;13895](https://redirect.github.com/pytest-dev/pytest/issues/13895):
        Restore support for skipping tests via `raise unittest.SkipTest`.\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
        The terminal progress plugin added in pytest 9.0 is now automatically disabled
        when iTerm2 is detected, it generated desktop notifications instead of the
        desired functionality.\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
        Fixed the TOML type of the verbosity settings in the API reference from number
        to string.\n- [#&#8203;13910](https://redirect.github.com/pytest-dev/pytest/issues/13910):
        Fixed <span class=\"title-ref\">UserWarning: Do not expect file\\_or\\_dir</span>
        on some earlier Python 3.12 and 3.13 point versions.\n\n#### Packaging updates
        and notes for downstreams\n\n- [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
        The tox configuration has been adjusted to make sure the desired\n  version
        string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
        environment\n  variable as a part of the release process -- by `webknjaz`.\n\n####
        Contributor-facing changes\n\n- [#&#8203;13891](https://redirect.github.com/pytest-dev/pytest/issues/13891),
        [#&#8203;13942](https://redirect.github.com/pytest-dev/pytest/issues/13942):
        The CI/CD part of the release automation is now capable of\n  creating GitHub
        Releases without having a Git checkout on\n  disk -- by `bluetech` and `webknjaz`.\n-
        [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
        The tox configuration has been adjusted to make sure the desired\n  version
        string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
        environment\n  variable as a part of the release process -- by `webknjaz`.\n\n###
        [`v9.0.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.0)\n\n[Compare
        Source](https://redirect.github.com/pytest-dev/pytest/compare/8.4.2...9.0.0)\n\n###
        pytest 9.0.0 (2025-11-05)\n\n#### New features\n\n- [#&#8203;1367](https://redirect.github.com/pytest-dev/pytest/issues/1367):
        **Support for subtests** has been added.\n\n  `subtests <subtests>` are an
        alternative to parametrization, useful in situations where the parametrization
        values are not all known at collection time.\n\n  Example:\n\n  ```python\n
        \ def contains_docstring(p: Path) -> bool:\n      \"\"\"Return True if the
        given Python file contains a top-level docstring.\"\"\"\n      ...\n\n  def
        test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:\n      for
        path in Path.cwd().glob(\"*.py\"):\n          with subtests.test(path=str(path)):\n
        \             assert contains_docstring(path)\n  ```\n\n  Each assert failure
        or error is caught by the context manager and reported individually, giving
        a clear picture of all files that are missing a docstring.\n\n  In addition,
        `unittest.TestCase.subTest` is now also supported.\n\n  This feature was originally
        implemented as a separate plugin in [pytest-subtests](https://redirect.github.com/pytest-dev/pytest-subtests),
        but since then has been merged into the core.\n\n  > \\[!NOTE]\n  > This feature
        is experimental and will likely evolve in future releases. By that we mean
        that we might change how subtests are reported on failure, but the functionality
        and how to use it are stable.\n\n- [#&#8203;13743](https://redirect.github.com/pytest-dev/pytest/issues/13743):
        Added support for **native TOML configuration files**.\n\n  While pytest,
        since version 6, supports configuration in `pyproject.toml` files under `[tool.pytest.ini_options]`,\n
        \ it does so in an \"INI compatibility mode\", where all configuration values
        are treated as strings or list of strings.\n  Now, pytest supports the native
        TOML data model.\n\n  In `pyproject.toml`, the native TOML configuration is
        under the `[tool.pytest]` table.\n\n  ```toml\n  # pyproject.toml\n  [tool.pytest]\n
        \ minversion = \"9.0\"\n  addopts = [\"-ra\", \"-q\"]\n  testpaths = [\n      \"tests\",\n
        \     \"integration\",\n  ]\n  ```\n\n  The `[tool.pytest.ini_options]` table
        remains supported, but both tables cannot be used at the same time.\n\n  If
        you prefer to use a separate configuration file, or don't use `pyproject.toml`,
        you can use `pytest.toml` or `.pytest.toml`:\n\n  ```toml\n  # pytest.toml
        or .pytest.toml\n  [pytest]\n  minversion = \"9.0\"\n  addopts = [\"-ra\",
        \"-q\"]\n  testpaths = [\n      \"tests\",\n      \"integration\",\n  ]\n
        \ ```\n\n  The documentation now (sometimes) shows configuration snippets
        in both TOML and INI formats, in a tabbed interface.\n\n  See `config file
        formats` for full details.\n\n- [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
        Added a **\"strict mode\"** enabled by the `strict` configuration option.\n\n
        \ When set to `true`, the `strict` option currently enables\n\n  - `strict_config`\n
        \ - `strict_markers`\n  - `strict_parametrization_ids`\n  - `strict_xfail`\n\n
        \ The individual strictness options can be explicitly set to override the
        global `strict` setting.\n\n  The previously-deprecated `--strict` command-line
        flag now enables strict mode.\n\n  If pytest adds new strictness options in
        the future, they will also be enabled in strict mode.\n  Therefore, you should
        only enable strict mode if you use a pinned/locked version of pytest,\n  or
        if you want to proactively adopt new strictness options as they are added.\n\n
        \ See `strict mode` for more details.\n\n- [#&#8203;13737](https://redirect.github.com/pytest-dev/pytest/issues/13737):
        Added the `strict_parametrization_ids` configuration option.\n\n  When set,
        pytest emits an error if it detects non-unique parameter set IDs,\n  rather
        than automatically making the IDs unique by adding <span class=\"title-ref\">0</span>,
        <span class=\"title-ref\">1</span>, ... to them.\n  This can be particularly
        useful for catching unintended duplicates.\n\n- [#&#8203;13072](https://redirect.github.com/pytest-dev/pytest/issues/13072):
        Added support for displaying test session **progress in the terminal tab**
        using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC)
        ANSI sequence.\n  When pytest runs in a supported terminal emulator like ConEmu,
        Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,\n  you'll see
        the progress in the terminal tab or window,\n  allowing you to monitor pytest's
        progress at a glance.\n\n  This feature is automatically enabled when running
        in a TTY. It is implemented as an internal plugin. If needed, it can be disabled
        as follows:\n\n  - On a user level, using `-p no:terminalprogress` on the
        command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`.\n
        \ - On a project configuration level, using `addopts = \"-p no:terminalprogress\"`.\n\n-
        [#&#8203;478](https://redirect.github.com/pytest-dev/pytest/issues/478): Support
        PEP420 (implicit namespace packages) as <span class=\"title-ref\">--pyargs</span>
        target when `consider_namespace_packages` is <span class=\"title-ref\">true</span>
        in the config.\n\n  Previously, this option only impacted package imports,
        now it also impacts tests discovery.\n\n- [#&#8203;13678](https://redirect.github.com/pytest-dev/pytest/issues/13678):
        Added a new `faulthandler_exit_on_timeout` configuration option set to \"false\"
        by default to let <span class=\"title-ref\">faulthandler</span> interrupt
        the <span class=\"title-ref\">pytest</span> process after a timeout in case
        of deadlock.\n\n  Previously, a <span class=\"title-ref\">faulthandler</span>
        timeout would only dump the traceback of all threads to stderr, but would
        not interrupt the <span class=\"title-ref\">pytest</span> process.\n\n  \\--
        by `ogrisel`.\n\n- [#&#8203;13829](https://redirect.github.com/pytest-dev/pytest/issues/13829):
        Added support for configuration option aliases via the `aliases` parameter
        in `Parser.addini() <pytest.Parser.addini>`.\n\n  Plugins can now register
        alternative names for configuration options,\n  allowing for more flexibility
        in configuration naming and supporting backward compatibility when renaming
        options.\n  The canonical name always takes precedence if both the canonical
        name and an alias are specified in the configuration file.\n\n#### Improvements
        in existing functionality\n\n- [#&#8203;13330](https://redirect.github.com/pytest-dev/pytest/issues/13330):
        Having pytest configuration spread over more than one file (for example having
        both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]`
        table) will now print a warning to make it clearer to the user that only one
        of them is actually used.\n\n  \\-- by `sgaist`\n\n- [#&#8203;13574](https://redirect.github.com/pytest-dev/pytest/issues/13574):
        The single argument `--version` no longer loads the entire plugin infrastructure,
        making it faster and more reliable when displaying only the pytest version.\n\n
        \ Passing `--version` twice (e.g., `pytest --version --version`) retains the
        original behavior, showing both the pytest version and plugin information.\n\n
        \ > \\[!NOTE]\n  > Since `--version` is now processed early, it only takes
        effect when passed directly via the command line. It will not work if set
        through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`.\n\n- [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
        Added `strict_xfail` as an alias to the `xfail_strict` option,\n  `strict_config`
        as an alias to the `--strict-config` flag,\n  and `strict_markers` as an alias
        to the `--strict-markers` flag.\n  This makes all strictness options consistently
        have configuration options with the prefix `strict_`.\n\n- [#&#8203;13700](https://redirect.github.com/pytest-dev/pytest/issues/13700):
        <span class=\"title-ref\">--junitxml</span> no longer prints the <span class=\"title-ref\">generated
        xml file</span> summary at the end of the pytest session when <span class=\"title-ref\">--quiet</span>
        is given.\n\n- [#&#8203;13732](https://redirect.github.com/pytest-dev/pytest/issues/13732):
        Previously, when filtering warnings, pytest would fail if the filter referenced
        a class that could not be imported. Now, this only outputs a message indicating
        the problem.\n\n- [#&#8203;13859](https://redirect.github.com/pytest-dev/pytest/issues/13859):
        Clarify the error message for <span class=\"title-ref\">pytest.raises()</span>
        when a regex <span class=\"title-ref\">match</span> fails.\n\n- [#&#8203;13861](https://redirect.github.com/pytest-dev/pytest/issues/13861):
        Better sentence structure in a test's expected error message. Previously,
        the error message would be \"expected exception must be \\<expected>, but
        got \\<actual>\". Now, it is \"Expected \\<expected>, but got \\<actual>\".\n\n####
        Removals and backward incompatible breaking changes\n\n- [#&#8203;12083](https://redirect.github.com/pytest-dev/pytest/issues/12083):
        Fixed a bug where an invocation such as <span class=\"title-ref\">pytest a/
        a/b</span> would cause only tests from <span class=\"title-ref\">a/b</span>
        to run, and not other tests under <span class=\"title-ref\">a/</span>.\n\n
        \ The fix entails a few breaking changes to how such overlapping arguments
        and duplicates are handled:\n\n  1. <span class=\"title-ref\">pytest a/b a/</span>
        or <span class=\"title-ref\">pytest a/ a/b</span> are equivalent to <span
        class=\"title-ref\">pytest a</span>; if an argument overlaps another arguments,
        only the prefix remains.\n  2. <span class=\"title-ref\">pytest x.py x.py</span>
        is equivalent to <span class=\"title-ref\">pytest x.py</span>; previously
        such an invocation was taken as an explicit request to run the tests from
        the file twice.\n\n  If you rely on these behaviors, consider using `--keep-duplicates
        <duplicate-paths>`, which retains its existing behavior (including the bug).\n\n-
        [#&#8203;13719](https://redirect.github.com/pytest-dev/pytest/issues/13719):
        Support for Python 3.9 is dropped following its end of life.\n\n- [#&#8203;13766](https://redirect.github.com/pytest-dev/pytest/issues/13766):
        Previously, pytest would assume it was running in a CI/CD environment if either
        of the environment variables <span class=\"title-ref\">$CI</span> or <span
        class=\"title-ref\">$BUILD\\_NUMBER</span> was defined;\n  now, CI mode is
        only activated if at least one of those variables is defined and set to a
        *non-empty* value.\n\n- [#&#8203;13779](https://redirect.github.com/pytest-dev/pytest/issues/13779):
        **PytestRemovedIn9Warning deprecation warnings are now errors by default.**\n\n
        \ Following our plan to remove deprecated features with as little disruption
        as\n  possible, all warnings of type `PytestRemovedIn9Warning` now generate
        errors\n  instead of warning messages by default.\n\n  **The affected features
        will be effectively removed in pytest 9.1**, so please consult the\n  `deprecations`
        section in the docs for directions on how to update existing code.\n\n  In
        the pytest `9.0.X` series, it is possible to change the errors back into warnings
        as a\n  stopgap measure by adding this to your `pytest.ini` file:\n\n  ```ini\n
        \ [pytest]\n  filterwarnings =\n      ignore::pytest.PytestRemovedIn9Warning\n
        \ ```\n\n  But this will stop working when pytest `9.1` is released.\n\n  **If
        you have concerns** about the removal of a specific feature, please add a\n
        \ comment to `13779`.\n\n#### Deprecations (removal in next major release)\n\n-
        [#&#8203;13807](https://redirect.github.com/pytest-dev/pytest/issues/13807):
        `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now issues
        a deprecation warning when the prepended path contains legacy namespace packages
        (those using `pkg_resources.declare_namespace()`).\n  Users should migrate
        to native namespace packages (`420`).\n  See `monkeypatch-fixup-namespace-packages`
        for details.\n\n#### Bug fixes\n\n- [#&#8203;13445](https://redirect.github.com/pytest-dev/pytest/issues/13445):
        Made the type annotations of `pytest.skip` and friends more spec-complaint
        to have them work across more type checkers.\n\n- [#&#8203;13537](https://redirect.github.com/pytest-dev/pytest/issues/13537):
        Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in teardown
        was not handled correctly and showed as error.\n\n- [#&#8203;13598](https://redirect.github.com/pytest-dev/pytest/issues/13598):
        Fixed possible collection confusion on Windows when short paths and symlinks
        are involved.\n\n- [#&#8203;13716](https://redirect.github.com/pytest-dev/pytest/issues/13716):
        Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file cannot
        be parametrized) was silently treated as `pytest x.py`. This is now a usage
        error.\n\n- [#&#8203;13722](https://redirect.github.com/pytest-dev/pytest/issues/13722):
        Fixed a misleading assertion failure message when using `pytest.approx` on
        mappings with differing lengths.\n\n- [#&#8203;13773](https://redirect.github.com/pytest-dev/pytest/issues/13773):
        Fixed the static fixture closure calculation to properly consider transitive
        dependencies requested by overridden fixtures.\n\n- [#&#8203;13816](https://redirect.github.com/pytest-dev/pytest/issues/13816):
        Fixed `pytest.approx` which now returns a clearer error message when comparing
        mappings with different keys.\n\n- [#&#8203;13849](https://redirect.github.com/pytest-dev/pytest/issues/13849):
        Hidden `.pytest.ini` files are now picked up as the config file even if empty.\n
        \ This was an inconsistency with non-hidden `pytest.ini`.\n\n- [#&#8203;13865](https://redirect.github.com/pytest-dev/pytest/issues/13865):
        Fixed <span class=\"title-ref\">--show-capture</span> with <span class=\"title-ref\">--tb=line</span>.\n\n-
        [#&#8203;13522](https://redirect.github.com/pytest-dev/pytest/issues/13522):
        Fixed `pytester` in subprocess mode ignored all :attr\\`pytester.plugins \\<pytest.Pytester.plugins>\\`
        except the first.\n\n  Fixed `pytester` in subprocess mode silently ignored
        non-str `pytester.plugins <pytest.Pytester.plugins>`.\n  Now it errors instead.\n
        \ If you are affected by this, specify the plugin by name, or switch the affected
        tests to use `pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess>`
        explicitly instead.\n\n#### Packaging updates and notes for downstreams\n\n-
        [#&#8203;13791](https://redirect.github.com/pytest-dev/pytest/issues/13791):
        Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1`
        and `22.0.0`, respectively.\n\n#### Contributor-facing changes\n\n- [#&#8203;12244](https://redirect.github.com/pytest-dev/pytest/issues/12244):
        Fixed self-test failures when <span class=\"title-ref\">TERM=dumb</span>.\n-
        [#&#8203;12474](https://redirect.github.com/pytest-dev/pytest/issues/12474):
        Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation.\n-
        [#&#8203;13621](https://redirect.github.com/pytest-dev/pytest/issues/13621):
        pytest's own testsuite now handles the `lsof` command hanging (e.g. due to
        unreachable network filesystems), with the affected selftests being skipped
        after 10 seconds.\n- [#&#8203;13638](https://redirect.github.com/pytest-dev/pytest/issues/13638):
        Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`.\n
        \ The script now uses `gh pr create` which is compatible with GitHub CLI v2.0+.\n-
        [#&#8203;13695](https://redirect.github.com/pytest-dev/pytest/issues/13695):
        Flush <span class=\"title-ref\">stdout</span> and <span class=\"title-ref\">stderr</span>
        in <span class=\"title-ref\">Pytester.run</span> to avoid truncated outputs
        in <span class=\"title-ref\">test\\_faulthandler.py::test\\_timeout</span>
        on CI -- by `ogrisel`.\n- [#&#8203;13771](https://redirect.github.com/pytest-dev/pytest/issues/13771):
        Skip <span class=\"title-ref\">test\\_do\\_not\\_collect\\_symlink\\_siblings</span>
        on Windows environments without symlink support to avoid false negatives.\n-
        [#&#8203;13841](https://redirect.github.com/pytest-dev/pytest/issues/13841):
        `tox>=4` is now required when contributing to pytest.\n- [#&#8203;13625](https://redirect.github.com/pytest-dev/pytest/issues/13625):
        Added missing docstrings to `pytest_addoption()`, `pytest_configure()`, and
        `cacheshow()` functions in `cacheprovider.py`.\n\n#### Miscellaneous internal
        changes\n\n- [#&#8203;13830](https://redirect.github.com/pytest-dev/pytest/issues/13830):
        Configuration overrides (`-o`/`--override-ini`) are now processed during startup
        rather than during `config.getini() <pytest.Config.getini>`.\n\n</details>\n\n---\n\n###
        Configuration\n\n\U0001F4C5 **Schedule**: (UTC)\n\n- Branch creation\n  -
        At any time (no schedule defined)\n- Automerge\n  - At any time (no schedule
        defined)\n\n\U0001F6A6 **Automerge**: Disabled by config. Please merge this
        manually once you are satisfied.\n\n\u267B **Rebasing**: Whenever PR becomes
        conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F515 **Ignore**:
        Close this PR and you won't be reminded about this update again.\n\n---\n\n
        - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this
        box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
        View the [repository job log](https://developer.mend.io/github/osism/ansible-collection-services).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
      change_url: https://github.com/osism/ansible-collection-services/pull/2103
      child_jobs: []
      commit_id: db85d442c9f545811efe766d1b18b2a74c53c358
      event_id: e56785c0-69b5-11f1-87ad-883a9ef81791
      executor:
        hostname: 521e9411259a
        inventory_file: /var/lib/zuul/builds/522ded43842c45cb816e3fa48e02801e/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/522ded43842c45cb816e3fa48e02801e/work/logs
        result_data_file: /var/lib/zuul/builds/522ded43842c45cb816e3fa48e02801e/work/results.json
        src_root: /var/lib/zuul/builds/522ded43842c45cb816e3fa48e02801e/work/src
        work_root: /var/lib/zuul/builds/522ded43842c45cb816e3fa48e02801e/work
      include_vars: []
      items:
      - branch: main
        change: '2103'
        change_message: "chore(deps): update dependency pytest to v9\n\nThis PR contains
          the following updates:\n\n| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|\n|
          [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html))
          | `==8.4.2` \u2192 `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/8.4.2/9.1.0?slim=true)
          |\n\n---\n\n> [!WARNING]\n> Some dependencies could not be looked up. Check
          the [Dependency Dashboard](../issues/293) for more information.\n\n---\n\n###
          Release Notes\n\n<details>\n<summary>pytest-dev/pytest (pytest)</summary>\n\n###
          [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)\n\n#####
          pytest 9.1.0 (2026-06-13)\n\n##### Removals and backward incompatible breaking
          changes\n\n- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  If this is undesirable,
          move the fixture definition to a `conftest.py` file if possible.\n\n  Technical
          explanation for those interested:\n  When using <span class=\"title-ref\">--doctest-modules</span>,
          pytest possibly collects Python modules twice, once as `pytest.Module` and
          once as a `DoctestModule` (depending on the configuration).\n  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`.\n  This
          means that both need to register the fixtures independently.\n\n##### Deprecations
          (removal in next major release)\n\n- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n  See `10819` and
          `14011`.\n\n- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  See `dynamic-fixture-request-during-teardown`
          for details.\n\n- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  These iterables get exhausted after the first iteration,\n
          \ leading to tests getting unexpectedly skipped in cases such as running
          `pytest.main()` multiple times,\n  using class-level parametrize decorators,\n
          \ or collecting tests multiple times.\n\n  See `parametrize-iterators` for
          details and suggestions.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute is now deprecated.\n  Use `config.getini()
          <pytest.Config.getini>` to access configuration values instead.\n\n  See
          `config-inicfg` for more details.\n\n- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n  Use the `node` parameter instead for fixture
          scoping. This enables more robust node-based\n  matching instead of string
          prefix matching.\n  If you've used `nodeid=None`, pass `node=session` instead.\n\n
          \ This will be removed in pytest 10.\n\n- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/14335):
          The method of configuring hooks using markers, deprecated since pytest 7.2,
          is now scheduled to be removed in pytest 10.\n  See `hook-markers` for more
          details.\n\n- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/14434):
          The `--pastebin` option is now deprecated.\n  The same functionality is
          now available in an external plugin, `pytest-pastebin`.\n  See `pastebin-deprecated`
          for more details.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The private `FixtureDef.has_location` attribute is now deprecated and will
          be removed in pytest 10.\n  See `fixturedef-has-location-deprecated` for
          details.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          `pytest.console_main` is now deprecated and will be removed in pytest 10.\n
          \ It was never intended for programmatic use; use `pytest.main` instead.\n\n#####
          New features\n\n- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/12376):
          Added `pytest.register_fixture()` to register fixtures using an imperative
          interface.\n\n  This is an advanced function intended for use by plugins.\n\n
          \ Normally, fixtures should be registered declaratively using the `@pytest.fixture
          <pytest.fixture>` decorator.\n  Pytest looks for these fixture definitions
          during the collection phase and registers them automatically.\n  For some
          plugin usecases the declarative interface can be cumbersome or unviable,
          in which case this imperative interface can be used.\n\n- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023):
          Added <span class=\"title-ref\">--report-chars</span> long CLI option.\n\n-
          [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/6757):
          Added the `assertion_text_diff_style` configuration option, allowing\n  string
          equality failures to be rendered as separate `Left:` and `Right:`\n  blocks
          instead of `ndiff` output.\n\n- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/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`.\n\n##### Improvements in existing functionality\n\n-
          [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
          [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295):
          Improved output of `--fixtures-per-test` by excluding internal-implementation
          fixtures generated by `@pytest.mark.parametrize` and similar.\n\n- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/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.\n  `func` can now also be passed as a kwarg, which
          the type hint previously showed as possible but didn't accept.\n\n- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862):
          Improved the readability of \"DID NOT RAISE\" error messages by using the
          exception type's name instead of its <span class=\"title-ref\">repr</span>.\n\n-
          [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026):
          Added test coverage for compiled regex patterns in `pytest.raises` match
          parameter.\n\n- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137):
          <span class=\"title-ref\">pytest.ScopeName</span> is now public to allow
          using it in function signatures.\n\n- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/14342):
          Marked `yield_fixture` as deprecated to type checkers using the `deprecated`
          decorator. Note it\n  `has originally been deprecated <yield-fixture-deprecated>`
          in pytest 6.2 already.\n\n- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373):
          Added type annotations for `pytest.approx`.\n\n- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/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.\n\n-
          [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461):
          Improved assertion failure explanations for equality comparisons between
          mapping objects that are not `dict` instances.\n\n- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513):
          The order in which fixture definitions overriding each other are resolved
          is now determined first by their *visibility* in the collection tree rather
          than by the order in which they are registered.\n\n  A fixture defined for
          a more specific node (e.g. a module or an item) now always takes precedence
          over one with the same name defined for a more general node (e.g. the session),
          even when the more general one was registered later.\n  Fixtures with non-comparable
          visibility or the same visibility keep the existing behavior of \"last registered
          wins\".\n  This change is supposed to only affect plugins which register
          multiple fixtures programmatically with the same name.\n\n- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524):
          Add official Python 3.15 support.\n\n- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764):
          Improved argparse program name to show `pytest`, `python -m pytest`, or
          `pytest.main()` based on how pytest was invoked, making help and error messages
          clearer.\n\n- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265):
          Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns
          `None` for `pytestmark` instead of raising `AttributeError`.\n\n  Previously
          this caused a cryptic `TypeError: got None instead of Mark` error.\n  Now
          pytest issues a helpful warning and continues collecting the module normally.\n\n#####
          Bug fixes\n\n- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192):
          Fixed <span class=\"title-ref\">|</span> (pipe) not being treated as a regex
          meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.\n\n-
          [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484):
          Fixed `-W` option values being duplicated in `Config.known_args_namespace`.\n\n-
          [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626):
          Fixed function-scoped fixture values being kept alive after a test was interrupted
          by `KeyboardInterrupt` or early exit,\n  allowing them to potentially be
          released more promptly.\n\n- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784):
          Fixed `capteesys` producing doubled output when used with `--capture=no`
          (`-s`).\n\n- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817):
          Fixed a secondary <span class=\"title-ref\">AttributeError</span> masking
          the original error when an option argument fails to initialize.\n\n- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884):
          Fixed rare internal IndexError caused by <span class=\"title-ref\">builtins.compile</span>
          being overridden in client code.\n\n- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885):
          Fixed autouse fixtures defined inside a `unittest.TestCase` class running
          even when the class is decorated with `unittest.skip` or `unittest.skipIf`
          -- regression since pytest 8.1.0.\n\n- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917):
          `unittest.SkipTest` is no longer considered an interactive exception, i.e.
          `pytest_exception_interact` is no longer called for it.\n\n- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963):
          Fixed subtests running with `pytest-xdist` when their contexts contain objects
          that are not JSON-serializable.\n\n  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).\n\n-
          [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004):
          Fixed conftest.py fixture scoping when `testpaths` points outside of the
          `rootdir <rootdir>`.\n\n  Previously, fixtures from nested conftest.py files
          would incorrectly leak to sibling directories\n  when using a relative `testpaths`
          like `../tests/sdk`.\n\n  Conftest fixtures are now parsed during `Directory
          <pytest.Directory>` collection, using the `Directory` node for proper scoping.\n\n-
          [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050):
          Display dictionary differences in assertion failures using the original
          key insertion order instead of sorted order.\n\n- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080):
          fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile`
          methods.\n\n- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114):
          An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures
          from being torn down, causing additional errors in the following tests.\n\n-
          [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161):
          Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale
          entry on the undo stack when the underlying `setattr()` call fails (e.g.
          on immutable targets), causing an `AttributeError` crash during teardown.\n\n-
          [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214):
          Fixed `-v` hint in `pytest.raises` match diff not working because assertion
          verbosity was not propagated.\n\n- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234):
          Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...)
          <pytest.mark.parametrize ref>` typing.\n\n- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248):
          Fixed direct parametrization causing the static fixture closure (as reflected
          in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit
          fixtures that are requested transitively from overridden fixtures.\n\n-
          [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263):
          Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`,
          before pytest tears down the warning filters installed for the session.
          Previously the collection ran from a cleanup callback whose order relative
          to other plugins' cleanups was not guaranteed, so an active `error` filter
          could be removed before the exception surfaced and a late resource leak
          would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`,
          now promotes these exceptions to failures regardless of plugin cleanup order.\n\n-
          [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377):
          Fixed crash in <span class=\"title-ref\">Config.get\\_terminal\\_writer</span>
          when an assertion fails with the `terminalreporter` plugin disabled.\n\n-
          [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381):
          Fixed `-V` (short form of `--version`) to properly display the current version.\n\n-
          [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389):
          Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress
          the mismatched exception as a cause of the resulting `AssertionError`.\n\n-
          [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392):
          Fixed a bug in `pytest.raises(match=...) <pytest.raises>` \"fully escaped\"
          detection, causing the regex diff display to be shown in some instances
          when the raw string diff display should be shown instead.\n\n- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442):
          Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config`
          specified through `addopts` were silently ignored.\n\n  Note that when targeting
          pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or
          `strict mode <strict mode>`.\n\n- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456):
          Fixed `pytest.approx` not recognizing types with `__array_interface__` as
          numpy-like arrays.\n\n- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474):
          Fixed a regression where `-k` and `-m` expressions containing both backslash
          characters in identifiers and string literal arguments would incorrectly
          raise a `SyntaxError` about escaping.\n\n- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483):
          Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary
          plane characters like emoji) in test failure messages. -- by `EternalRights`\n\n-
          [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492):
          Fixed `Code.getargs()` incorrectly including local variable names in the
          returned argument tuple for functions with `*args` and/or `**kwargs`. The
          method was using `co_flags` bitmask values (`4` and `8`) directly as counts
          instead of converting them to `1` via `bool()`, and was not accounting for
          `co_kwonlyargcount` when `var=True`.\n\n- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697):
          Logging capture now works for non-propagating loggers.\n  Previously only
          logs which reached the root logger were captured.\n  This includes `caplog`
          and the \"Captured log calls\" test reporting.\n\n- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850):
          Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element
          now always matches the number of `<testcase>` elements in the file. In some
          cases (test passes but fails during teardown) the `tests` attribute would
          report an incorrect number of testcases in the XML file.\n\n- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848):
          `pytest_fixture_post_finalizer` is no longer called extra times for the
          same fixture teardown in some cases.\n\n- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719):
          Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking
          single-element tuple values when using a string argnames with a trailing
          comma (e.g., `\"arg,\"`).\n\n  The trailing comma form now correctly behaves
          like the tuple form `(\"arg\",)`, treating argvalues as a list of tuples
          to unpack.\n\n##### Improved documentation\n\n- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022):
          Document safer alternatives and scope guidance for monkeypatching standard
          library functions.\n- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307):
          Document that `@pytest.hookimpl(specname=...)` only works for function names
          starting with `pytest_`.\n- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038):
          Document that doctests do not support parametrized fixtures, including parametrized
          autouse fixtures.\n- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155):
          Clarified how the `request` fixture provides indirect parametrization values
          via `request.param`.\n- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304):
          Clarified in the documentation that hook implementations defined in `conftest.py`
          files are not available to other plugins during their `pytest_addoption()`
          execution, as conftest files are discovered and loaded after builtin and
          third-party plugins have been initialized. However, initial conftest files
          themselves can implement `pytest_addoption()` to add their own command-line
          options.\n- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902):
          Clarified how subtest progress markers are shown in the documentation.\n-
          [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012):
          The `ini options ref` section of the API Reference now specified the type
          and default value of every configuration option.\n- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148):
          Documented a safe `pytestconfig.cache` access pattern when the\n  `cacheprovider`
          plugin is disabled.\n- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303):
          The documentation is now built with Sphinx >= 9.\n- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465):
          Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist`
          at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout.
          Pointing at a tag keeps the example in sync with the version users actually
          install, while remaining stable when the project's main branch moves on.\n\n#####
          Miscellaneous internal changes\n\n- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582):
          Improved the recursion traceback test to exercise all requested traceback
          styles.\n\n### [`v9.0.3`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.3)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.2...9.0.3)\n\n###
          pytest 9.0.3 (2026-04-07)\n\n#### Bug fixes\n\n- [#&#8203;12444](https://redirect.github.com/pytest-dev/pytest/issues/12444):
          Fixed `pytest.approx` which now correctly takes into account `~collections.abc.Mapping`
          keys order to compare them.\n\n- [#&#8203;13634](https://redirect.github.com/pytest-dev/pytest/issues/13634):
          Blocking a `conftest.py` file using the `-p no:` option is now explicitly
          disallowed.\n\n  Previously this resulted in an internal assertion failure
          during plugin loading.\n\n  Pytest now raises a clear `UsageError` explaining
          that conftest files are not plugins and cannot be disabled via `-p`.\n\n-
          [#&#8203;13734](https://redirect.github.com/pytest-dev/pytest/issues/13734):
          Fixed crash when a test raises an exceptiongroup with `__tracebackhide__
          = True`.\n\n- [#&#8203;14195](https://redirect.github.com/pytest-dev/pytest/issues/14195):
          Fixed an issue where non-string messages passed to <span class=\"title-ref\">unittest.TestCase.subTest()</span>
          were not printed.\n\n- [#&#8203;14343](https://redirect.github.com/pytest-dev/pytest/issues/14343):
          Fixed use of insecure temporary directory (CVE-2025-71176).\n\n#### Improved
          documentation\n\n- [#&#8203;13388](https://redirect.github.com/pytest-dev/pytest/issues/13388):
          Clarified documentation for `-p` vs `PYTEST_PLUGINS` plugin loading and
          fixed an incorrect `-p` example.\n- [#&#8203;13731](https://redirect.github.com/pytest-dev/pytest/issues/13731):
          Clarified that capture fixtures (e.g. `capsys` and `capfd`) take precedence
          over the `-s` / `--capture=no` command-line options in `Accessing captured
          output from a test function <accessing-captured-output>`.\n- [#&#8203;14088](https://redirect.github.com/pytest-dev/pytest/issues/14088):
          Clarified that the default `pytest_collection` hook sets `session.items`
          before it calls `pytest_collection_finish`, not after.\n- [#&#8203;14255](https://redirect.github.com/pytest-dev/pytest/issues/14255):
          TOML integer log levels must be quoted: Updating reference documentation.\n\n####
          Contributor-facing changes\n\n- [#&#8203;12689](https://redirect.github.com/pytest-dev/pytest/issues/12689):
          The test reports are now published to Codecov from GitHub Actions.\n  The
          test statistics is visible [on the web interface](https://app.codecov.io/gh/pytest-dev/pytest/tests).\n\n
          \ \\-- by `aleguy02`\n\n### [`v9.0.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.2)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.1...9.0.2)\n\n###
          pytest 9.0.2 (2025-12-06)\n\n#### Bug fixes\n\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
          The terminal progress feature added in pytest 9.0.0 has been disabled by
          default, except on Windows, due to compatibility issues with some terminal
          emulators.\n\n  You may enable it again by passing `-p terminalprogress`.
          We may enable it by default again once compatibility improves in the future.\n\n
          \ Additionally, when the environment variable `TERM` is `dumb`, the escape
          codes are no longer emitted, even if the plugin is enabled.\n\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
          Fixed the TOML type of the `tmp_path_retention_count` settings in the API
          reference from number to string.\n\n- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946):
          The private `config.inicfg` attribute was changed in a breaking manner in
          pytest 9.0.0.\n  Due to its usage in the ecosystem, it is now restored to
          working order using a compatibility shim.\n  It will be deprecated in pytest
          9.1 and removed in pytest 10.\n\n- [#&#8203;13965](https://redirect.github.com/pytest-dev/pytest/issues/13965):
          Fixed quadratic-time behavior when handling `unittest` subtests in Python
          3.10.\n\n#### Improved documentation\n\n- [#&#8203;4492](https://redirect.github.com/pytest-dev/pytest/issues/4492):
          The API Reference now contains cross-reference-able documentation of `pytest's
          command-line flags <command-line-flags>`.\n\n### [`v9.0.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.1)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.0...9.0.1)\n\n###
          pytest 9.0.1 (2025-11-12)\n\n#### Bug fixes\n\n- [#&#8203;13895](https://redirect.github.com/pytest-dev/pytest/issues/13895):
          Restore support for skipping tests via `raise unittest.SkipTest`.\n- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896):
          The terminal progress plugin added in pytest 9.0 is now automatically disabled
          when iTerm2 is detected, it generated desktop notifications instead of the
          desired functionality.\n- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904):
          Fixed the TOML type of the verbosity settings in the API reference from
          number to string.\n- [#&#8203;13910](https://redirect.github.com/pytest-dev/pytest/issues/13910):
          Fixed <span class=\"title-ref\">UserWarning: Do not expect file\\_or\\_dir</span>
          on some earlier Python 3.12 and 3.13 point versions.\n\n#### Packaging updates
          and notes for downstreams\n\n- [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
          The tox configuration has been adjusted to make sure the desired\n  version
          string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
          environment\n  variable as a part of the release process -- by `webknjaz`.\n\n####
          Contributor-facing changes\n\n- [#&#8203;13891](https://redirect.github.com/pytest-dev/pytest/issues/13891),
          [#&#8203;13942](https://redirect.github.com/pytest-dev/pytest/issues/13942):
          The CI/CD part of the release automation is now capable of\n  creating GitHub
          Releases without having a Git checkout on\n  disk -- by `bluetech` and `webknjaz`.\n-
          [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933):
          The tox configuration has been adjusted to make sure the desired\n  version
          string can be passed into its `package_env` through\n  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST`
          environment\n  variable as a part of the release process -- by `webknjaz`.\n\n###
          [`v9.0.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.0)\n\n[Compare
          Source](https://redirect.github.com/pytest-dev/pytest/compare/8.4.2...9.0.0)\n\n###
          pytest 9.0.0 (2025-11-05)\n\n#### New features\n\n- [#&#8203;1367](https://redirect.github.com/pytest-dev/pytest/issues/1367):
          **Support for subtests** has been added.\n\n  `subtests <subtests>` are
          an alternative to parametrization, useful in situations where the parametrization
          values are not all known at collection time.\n\n  Example:\n\n  ```python\n
          \ def contains_docstring(p: Path) -> bool:\n      \"\"\"Return True if the
          given Python file contains a top-level docstring.\"\"\"\n      ...\n\n  def
          test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:\n      for
          path in Path.cwd().glob(\"*.py\"):\n          with subtests.test(path=str(path)):\n
          \             assert contains_docstring(path)\n  ```\n\n  Each assert failure
          or error is caught by the context manager and reported individually, giving
          a clear picture of all files that are missing a docstring.\n\n  In addition,
          `unittest.TestCase.subTest` is now also supported.\n\n  This feature was
          originally implemented as a separate plugin in [pytest-subtests](https://redirect.github.com/pytest-dev/pytest-subtests),
          but since then has been merged into the core.\n\n  > \\[!NOTE]\n  > This
          feature is experimental and will likely evolve in future releases. By that
          we mean that we might change how subtests are reported on failure, but the
          functionality and how to use it are stable.\n\n- [#&#8203;13743](https://redirect.github.com/pytest-dev/pytest/issues/13743):
          Added support for **native TOML configuration files**.\n\n  While pytest,
          since version 6, supports configuration in `pyproject.toml` files under
          `[tool.pytest.ini_options]`,\n  it does so in an \"INI compatibility mode\",
          where all configuration values are treated as strings or list of strings.\n
          \ Now, pytest supports the native TOML data model.\n\n  In `pyproject.toml`,
          the native TOML configuration is under the `[tool.pytest]` table.\n\n  ```toml\n
          \ # pyproject.toml\n  [tool.pytest]\n  minversion = \"9.0\"\n  addopts =
          [\"-ra\", \"-q\"]\n  testpaths = [\n      \"tests\",\n      \"integration\",\n
          \ ]\n  ```\n\n  The `[tool.pytest.ini_options]` table remains supported,
          but both tables cannot be used at the same time.\n\n  If you prefer to use
          a separate configuration file, or don't use `pyproject.toml`, you can use
          `pytest.toml` or `.pytest.toml`:\n\n  ```toml\n  # pytest.toml or .pytest.toml\n
          \ [pytest]\n  minversion = \"9.0\"\n  addopts = [\"-ra\", \"-q\"]\n  testpaths
          = [\n      \"tests\",\n      \"integration\",\n  ]\n  ```\n\n  The documentation
          now (sometimes) shows configuration snippets in both TOML and INI formats,
          in a tabbed interface.\n\n  See `config file formats` for full details.\n\n-
          [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
          Added a **\"strict mode\"** enabled by the `strict` configuration option.\n\n
          \ When set to `true`, the `strict` option currently enables\n\n  - `strict_config`\n
          \ - `strict_markers`\n  - `strict_parametrization_ids`\n  - `strict_xfail`\n\n
          \ The individual strictness options can be explicitly set to override the
          global `strict` setting.\n\n  The previously-deprecated `--strict` command-line
          flag now enables strict mode.\n\n  If pytest adds new strictness options
          in the future, they will also be enabled in strict mode.\n  Therefore, you
          should only enable strict mode if you use a pinned/locked version of pytest,\n
          \ or if you want to proactively adopt new strictness options as they are
          added.\n\n  See `strict mode` for more details.\n\n- [#&#8203;13737](https://redirect.github.com/pytest-dev/pytest/issues/13737):
          Added the `strict_parametrization_ids` configuration option.\n\n  When set,
          pytest emits an error if it detects non-unique parameter set IDs,\n  rather
          than automatically making the IDs unique by adding <span class=\"title-ref\">0</span>,
          <span class=\"title-ref\">1</span>, ... to them.\n  This can be particularly
          useful for catching unintended duplicates.\n\n- [#&#8203;13072](https://redirect.github.com/pytest-dev/pytest/issues/13072):
          Added support for displaying test session **progress in the terminal tab**
          using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC)
          ANSI sequence.\n  When pytest runs in a supported terminal emulator like
          ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,\n  you'll
          see the progress in the terminal tab or window,\n  allowing you to monitor
          pytest's progress at a glance.\n\n  This feature is automatically enabled
          when running in a TTY. It is implemented as an internal plugin. If needed,
          it can be disabled as follows:\n\n  - On a user level, using `-p no:terminalprogress`
          on the command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`.\n
          \ - On a project configuration level, using `addopts = \"-p no:terminalprogress\"`.\n\n-
          [#&#8203;478](https://redirect.github.com/pytest-dev/pytest/issues/478):
          Support PEP420 (implicit namespace packages) as <span class=\"title-ref\">--pyargs</span>
          target when `consider_namespace_packages` is <span class=\"title-ref\">true</span>
          in the config.\n\n  Previously, this option only impacted package imports,
          now it also impacts tests discovery.\n\n- [#&#8203;13678](https://redirect.github.com/pytest-dev/pytest/issues/13678):
          Added a new `faulthandler_exit_on_timeout` configuration option set to \"false\"
          by default to let <span class=\"title-ref\">faulthandler</span> interrupt
          the <span class=\"title-ref\">pytest</span> process after a timeout in case
          of deadlock.\n\n  Previously, a <span class=\"title-ref\">faulthandler</span>
          timeout would only dump the traceback of all threads to stderr, but would
          not interrupt the <span class=\"title-ref\">pytest</span> process.\n\n  \\--
          by `ogrisel`.\n\n- [#&#8203;13829](https://redirect.github.com/pytest-dev/pytest/issues/13829):
          Added support for configuration option aliases via the `aliases` parameter
          in `Parser.addini() <pytest.Parser.addini>`.\n\n  Plugins can now register
          alternative names for configuration options,\n  allowing for more flexibility
          in configuration naming and supporting backward compatibility when renaming
          options.\n  The canonical name always takes precedence if both the canonical
          name and an alias are specified in the configuration file.\n\n#### Improvements
          in existing functionality\n\n- [#&#8203;13330](https://redirect.github.com/pytest-dev/pytest/issues/13330):
          Having pytest configuration spread over more than one file (for example
          having both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]`
          table) will now print a warning to make it clearer to the user that only
          one of them is actually used.\n\n  \\-- by `sgaist`\n\n- [#&#8203;13574](https://redirect.github.com/pytest-dev/pytest/issues/13574):
          The single argument `--version` no longer loads the entire plugin infrastructure,
          making it faster and more reliable when displaying only the pytest version.\n\n
          \ Passing `--version` twice (e.g., `pytest --version --version`) retains
          the original behavior, showing both the pytest version and plugin information.\n\n
          \ > \\[!NOTE]\n  > Since `--version` is now processed early, it only takes
          effect when passed directly via the command line. It will not work if set
          through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`.\n\n- [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823):
          Added `strict_xfail` as an alias to the `xfail_strict` option,\n  `strict_config`
          as an alias to the `--strict-config` flag,\n  and `strict_markers` as an
          alias to the `--strict-markers` flag.\n  This makes all strictness options
          consistently have configuration options with the prefix `strict_`.\n\n-
          [#&#8203;13700](https://redirect.github.com/pytest-dev/pytest/issues/13700):
          <span class=\"title-ref\">--junitxml</span> no longer prints the <span class=\"title-ref\">generated
          xml file</span> summary at the end of the pytest session when <span class=\"title-ref\">--quiet</span>
          is given.\n\n- [#&#8203;13732](https://redirect.github.com/pytest-dev/pytest/issues/13732):
          Previously, when filtering warnings, pytest would fail if the filter referenced
          a class that could not be imported. Now, this only outputs a message indicating
          the problem.\n\n- [#&#8203;13859](https://redirect.github.com/pytest-dev/pytest/issues/13859):
          Clarify the error message for <span class=\"title-ref\">pytest.raises()</span>
          when a regex <span class=\"title-ref\">match</span> fails.\n\n- [#&#8203;13861](https://redirect.github.com/pytest-dev/pytest/issues/13861):
          Better sentence structure in a test's expected error message. Previously,
          the error message would be \"expected exception must be \\<expected>, but
          got \\<actual>\". Now, it is \"Expected \\<expected>, but got \\<actual>\".\n\n####
          Removals and backward incompatible breaking changes\n\n- [#&#8203;12083](https://redirect.github.com/pytest-dev/pytest/issues/12083):
          Fixed a bug where an invocation such as <span class=\"title-ref\">pytest
          a/ a/b</span> would cause only tests from <span class=\"title-ref\">a/b</span>
          to run, and not other tests under <span class=\"title-ref\">a/</span>.\n\n
          \ The fix entails a few breaking changes to how such overlapping arguments
          and duplicates are handled:\n\n  1. <span class=\"title-ref\">pytest a/b
          a/</span> or <span class=\"title-ref\">pytest a/ a/b</span> are equivalent
          to <span class=\"title-ref\">pytest a</span>; if an argument overlaps another
          arguments, only the prefix remains.\n  2. <span class=\"title-ref\">pytest
          x.py x.py</span> is equivalent to <span class=\"title-ref\">pytest x.py</span>;
          previously such an invocation was taken as an explicit request to run the
          tests from the file twice.\n\n  If you rely on these behaviors, consider
          using `--keep-duplicates <duplicate-paths>`, which retains its existing
          behavior (including the bug).\n\n- [#&#8203;13719](https://redirect.github.com/pytest-dev/pytest/issues/13719):
          Support for Python 3.9 is dropped following its end of life.\n\n- [#&#8203;13766](https://redirect.github.com/pytest-dev/pytest/issues/13766):
          Previously, pytest would assume it was running in a CI/CD environment if
          either of the environment variables <span class=\"title-ref\">$CI</span>
          or <span class=\"title-ref\">$BUILD\\_NUMBER</span> was defined;\n  now,
          CI mode is only activated if at least one of those variables is defined
          and set to a *non-empty* value.\n\n- [#&#8203;13779](https://redirect.github.com/pytest-dev/pytest/issues/13779):
          **PytestRemovedIn9Warning deprecation warnings are now errors by default.**\n\n
          \ Following our plan to remove deprecated features with as little disruption
          as\n  possible, all warnings of type `PytestRemovedIn9Warning` now generate
          errors\n  instead of warning messages by default.\n\n  **The affected features
          will be effectively removed in pytest 9.1**, so please consult the\n  `deprecations`
          section in the docs for directions on how to update existing code.\n\n  In
          the pytest `9.0.X` series, it is possible to change the errors back into
          warnings as a\n  stopgap measure by adding this to your `pytest.ini` file:\n\n
          \ ```ini\n  [pytest]\n  filterwarnings =\n      ignore::pytest.PytestRemovedIn9Warning\n
          \ ```\n\n  But this will stop working when pytest `9.1` is released.\n\n
          \ **If you have concerns** about the removal of a specific feature, please
          add a\n  comment to `13779`.\n\n#### Deprecations (removal in next major
          release)\n\n- [#&#8203;13807](https://redirect.github.com/pytest-dev/pytest/issues/13807):
          `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now
          issues a deprecation warning when the prepended path contains legacy namespace
          packages (those using `pkg_resources.declare_namespace()`).\n  Users should
          migrate to native namespace packages (`420`).\n  See `monkeypatch-fixup-namespace-packages`
          for details.\n\n#### Bug fixes\n\n- [#&#8203;13445](https://redirect.github.com/pytest-dev/pytest/issues/13445):
          Made the type annotations of `pytest.skip` and friends more spec-complaint
          to have them work across more type checkers.\n\n- [#&#8203;13537](https://redirect.github.com/pytest-dev/pytest/issues/13537):
          Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in
          teardown was not handled correctly and showed as error.\n\n- [#&#8203;13598](https://redirect.github.com/pytest-dev/pytest/issues/13598):
          Fixed possible collection confusion on Windows when short paths and symlinks
          are involved.\n\n- [#&#8203;13716](https://redirect.github.com/pytest-dev/pytest/issues/13716):
          Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file
          cannot be parametrized) was silently treated as `pytest x.py`. This is now
          a usage error.\n\n- [#&#8203;13722](https://redirect.github.com/pytest-dev/pytest/issues/13722):
          Fixed a misleading assertion failure message when using `pytest.approx`
          on mappings with differing lengths.\n\n- [#&#8203;13773](https://redirect.github.com/pytest-dev/pytest/issues/13773):
          Fixed the static fixture closure calculation to properly consider transitive
          dependencies requested by overridden fixtures.\n\n- [#&#8203;13816](https://redirect.github.com/pytest-dev/pytest/issues/13816):
          Fixed `pytest.approx` which now returns a clearer error message when comparing
          mappings with different keys.\n\n- [#&#8203;13849](https://redirect.github.com/pytest-dev/pytest/issues/13849):
          Hidden `.pytest.ini` files are now picked up as the config file even if
          empty.\n  This was an inconsistency with non-hidden `pytest.ini`.\n\n- [#&#8203;13865](https://redirect.github.com/pytest-dev/pytest/issues/13865):
          Fixed <span class=\"title-ref\">--show-capture</span> with <span class=\"title-ref\">--tb=line</span>.\n\n-
          [#&#8203;13522](https://redirect.github.com/pytest-dev/pytest/issues/13522):
          Fixed `pytester` in subprocess mode ignored all :attr\\`pytester.plugins
          \\<pytest.Pytester.plugins>\\` except the first.\n\n  Fixed `pytester` in
          subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`.\n
          \ Now it errors instead.\n  If you are affected by this, specify the plugin
          by name, or switch the affected tests to use `pytester.runpytest_inprocess
          <pytest.Pytester.runpytest_inprocess>` explicitly instead.\n\n#### Packaging
          updates and notes for downstreams\n\n- [#&#8203;13791](https://redirect.github.com/pytest-dev/pytest/issues/13791):
          Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1`
          and `22.0.0`, respectively.\n\n#### Contributor-facing changes\n\n- [#&#8203;12244](https://redirect.github.com/pytest-dev/pytest/issues/12244):
          Fixed self-test failures when <span class=\"title-ref\">TERM=dumb</span>.\n-
          [#&#8203;12474](https://redirect.github.com/pytest-dev/pytest/issues/12474):
          Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo
          documentation.\n- [#&#8203;13621](https://redirect.github.com/pytest-dev/pytest/issues/13621):
          pytest's own testsuite now handles the `lsof` command hanging (e.g. due
          to unreachable network filesystems), with the affected selftests being skipped
          after 10 seconds.\n- [#&#8203;13638](https://redirect.github.com/pytest-dev/pytest/issues/13638):
          Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`.\n
          \ The script now uses `gh pr create` which is compatible with GitHub CLI
          v2.0+.\n- [#&#8203;13695](https://redirect.github.com/pytest-dev/pytest/issues/13695):
          Flush <span class=\"title-ref\">stdout</span> and <span class=\"title-ref\">stderr</span>
          in <span class=\"title-ref\">Pytester.run</span> to avoid truncated outputs
          in <span class=\"title-ref\">test\\_faulthandler.py::test\\_timeout</span>
          on CI -- by `ogrisel`.\n- [#&#8203;13771](https://redirect.github.com/pytest-dev/pytest/issues/13771):
          Skip <span class=\"title-ref\">test\\_do\\_not\\_collect\\_symlink\\_siblings</span>
          on Windows environments without symlink support to avoid false negatives.\n-
          [#&#8203;13841](https://redirect.github.com/pytest-dev/pytest/issues/13841):
          `tox>=4` is now required when contributing to pytest.\n- [#&#8203;13625](https://redirect.github.com/pytest-dev/pytest/issues/13625):
          Added missing docstrings to `pytest_addoption()`, `pytest_configure()`,
          and `cacheshow()` functions in `cacheprovider.py`.\n\n#### Miscellaneous
          internal changes\n\n- [#&#8203;13830](https://redirect.github.com/pytest-dev/pytest/issues/13830):
          Configuration overrides (`-o`/`--override-ini`) are now processed during
          startup rather than during `config.getini() <pytest.Config.getini>`.\n\n</details>\n\n---\n\n###
          Configuration\n\n\U0001F4C5 **Schedule**: (UTC)\n\n- Branch creation\n  -
          At any time (no schedule defined)\n- Automerge\n  - At any time (no schedule
          defined)\n\n\U0001F6A6 **Automerge**: Disabled by config. Please merge this
          manually once you are satisfied.\n\n\u267B **Rebasing**: Whenever PR becomes
          conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F515 **Ignore**:
          Close this PR and you won't be reminded about this update again.\n\n---\n\n
          - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this
          box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
          View the [repository job log](https://developer.mend.io/github/osism/ansible-collection-services).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->\n"
        change_url: https://github.com/osism/ansible-collection-services/pull/2103
        commit_id: db85d442c9f545811efe766d1b18b2a74c53c358
        patchset: db85d442c9f545811efe766d1b18b2a74c53c358
        project:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          name: osism/ansible-collection-services
          short_name: ansible-collection-services
          src_dir: src/github.com/osism/ansible-collection-services
        topic: null
      job: flake8
      jobtags: []
      max_attempts: 3
      message: chore(deps): update dependency pytest to v9

This PR contains the following updates:

| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `==8.4.2` → `==9.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest/9.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest/8.4.2/9.1.0?slim=true) |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency Dashboard](../issues/293) for more information.

---

### Release Notes

<details>
<summary>pytest-dev/pytest (pytest)</summary>

### [`v9.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.1.0)

[Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.3...9.1.0)

##### pytest 9.1.0 (2026-06-13)

##### Removals and backward incompatible breaking changes

- [#&#8203;14533](https://redirect.github.com/pytest-dev/pytest/issues/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 <span class="title-ref">--doctest-modules</span>, 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)

- [#&#8203;10819](https://redirect.github.com/pytest-dev/pytest/issues/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`.

- [#&#8203;12882](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;13409](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14335](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14434](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513): The private `FixtureDef.has_location` attribute is now deprecated and will be removed in pytest 10.
  See `fixturedef-has-location-deprecated` for details.

- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/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

- [#&#8203;12376](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14023](https://redirect.github.com/pytest-dev/pytest/issues/14023): Added <span class="title-ref">--report-chars</span> long CLI option.

- [#&#8203;14371](https://redirect.github.com/pytest-dev/pytest/issues/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`.

- [#&#8203;6757](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;8395](https://redirect.github.com/pytest-dev/pytest/issues/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

- [#&#8203;11225](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;11295](https://redirect.github.com/pytest-dev/pytest/issues/11295): Improved output of `--fixtures-per-test` by excluding internal-implementation fixtures generated by `@pytest.mark.parametrize` and similar.

- [#&#8203;13241](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;13862](https://redirect.github.com/pytest-dev/pytest/issues/13862): Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its <span class="title-ref">repr</span>.

- [#&#8203;14026](https://redirect.github.com/pytest-dev/pytest/issues/14026): Added test coverage for compiled regex patterns in `pytest.raises` match parameter.

- [#&#8203;14137](https://redirect.github.com/pytest-dev/pytest/issues/14137): <span class="title-ref">pytest.ScopeName</span> is now public to allow using it in function signatures.

- [#&#8203;14342](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14373](https://redirect.github.com/pytest-dev/pytest/issues/14373): Added type annotations for `pytest.approx`.

- [#&#8203;14430](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14441](https://redirect.github.com/pytest-dev/pytest/issues/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.

- [#&#8203;14461](https://redirect.github.com/pytest-dev/pytest/issues/14461): Improved assertion failure explanations for equality comparisons between mapping objects that are not `dict` instances.

- [#&#8203;14513](https://redirect.github.com/pytest-dev/pytest/issues/14513): The order in which fixture definitions overriding each other are resolved is now determined first by their *visibility* in the collection tree rather than by the order in which they are registered.

  A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later.
  Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins".
  This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name.

- [#&#8203;14524](https://redirect.github.com/pytest-dev/pytest/issues/14524): Add official Python 3.15 support.

- [#&#8203;1764](https://redirect.github.com/pytest-dev/pytest/issues/1764): Improved argparse program name to show `pytest`, `python -m pytest`, or `pytest.main()` based on how pytest was invoked, making help and error messages clearer.

- [#&#8203;8265](https://redirect.github.com/pytest-dev/pytest/issues/8265): Emit a `PytestCollectionWarning` when a module-level `__getattr__` returns `None` for `pytestmark` instead of raising `AttributeError`.

  Previously this caused a cryptic `TypeError: got None instead of Mark` error.
  Now pytest issues a helpful warning and continues collecting the module normally.

##### Bug fixes

- [#&#8203;13192](https://redirect.github.com/pytest-dev/pytest/issues/13192): Fixed <span class="title-ref">|</span> (pipe) not being treated as a regex meta-character that needs escaping in `pytest.raises(match=...) <pytest.raises>`.

- [#&#8203;13484](https://redirect.github.com/pytest-dev/pytest/issues/13484): Fixed `-W` option values being duplicated in `Config.known_args_namespace`.

- [#&#8203;13626](https://redirect.github.com/pytest-dev/pytest/issues/13626): Fixed function-scoped fixture values being kept alive after a test was interrupted by `KeyboardInterrupt` or early exit,
  allowing them to potentially be released more promptly.

- [#&#8203;13784](https://redirect.github.com/pytest-dev/pytest/issues/13784): Fixed `capteesys` producing doubled output when used with `--capture=no` (`-s`).

- [#&#8203;13817](https://redirect.github.com/pytest-dev/pytest/issues/13817): Fixed a secondary <span class="title-ref">AttributeError</span> masking the original error when an option argument fails to initialize.

- [#&#8203;13884](https://redirect.github.com/pytest-dev/pytest/issues/13884): Fixed rare internal IndexError caused by <span class="title-ref">builtins.compile</span> being overridden in client code.

- [#&#8203;13885](https://redirect.github.com/pytest-dev/pytest/issues/13885): Fixed autouse fixtures defined inside a `unittest.TestCase` class running even when the class is decorated with `unittest.skip` or `unittest.skipIf` -- regression since pytest 8.1.0.

- [#&#8203;13917](https://redirect.github.com/pytest-dev/pytest/issues/13917): `unittest.SkipTest` is no longer considered an interactive exception, i.e. `pytest_exception_interact` is no longer called for it.

- [#&#8203;13963](https://redirect.github.com/pytest-dev/pytest/issues/13963): Fixed subtests running with `pytest-xdist` when their contexts contain objects that are not JSON-serializable.

  Fixes [pytest-dev/pytest-xdist#1273](https://redirect.github.com/pytest-dev/pytest-xdist/issues/1273).

- [#&#8203;14004](https://redirect.github.com/pytest-dev/pytest/issues/14004): Fixed conftest.py fixture scoping when `testpaths` points outside of the `rootdir <rootdir>`.

  Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories
  when using a relative `testpaths` like `../tests/sdk`.

  Conftest fixtures are now parsed during `Directory <pytest.Directory>` collection, using the `Directory` node for proper scoping.

- [#&#8203;14050](https://redirect.github.com/pytest-dev/pytest/issues/14050): Display dictionary differences in assertion failures using the original key insertion order instead of sorted order.

- [#&#8203;14080](https://redirect.github.com/pytest-dev/pytest/issues/14080): fix missing type annotations on `Pytester.makepyfile` and `Pytester.maketxtfile` methods.

- [#&#8203;14114](https://redirect.github.com/pytest-dev/pytest/issues/14114): An exception from `pytest_fixture_post_finalizer` no longer prevents fixtures from being torn down, causing additional errors in the following tests.

- [#&#8203;14161](https://redirect.github.com/pytest-dev/pytest/issues/14161): Fixed `monkeypatch.setattr() <pytest.MonkeyPatch.setattr>` leaving a stale entry on the undo stack when the underlying `setattr()` call fails (e.g. on immutable targets), causing an `AttributeError` crash during teardown.

- [#&#8203;14214](https://redirect.github.com/pytest-dev/pytest/issues/14214): Fixed `-v` hint in `pytest.raises` match diff not working because assertion verbosity was not propagated.

- [#&#8203;14234](https://redirect.github.com/pytest-dev/pytest/issues/14234): Allow `pytest.HIDDEN_PARAM <hidden-param>` in `@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>` typing.

- [#&#8203;14248](https://redirect.github.com/pytest-dev/pytest/issues/14248): Fixed direct parametrization causing the static fixture closure (as reflected in `request.fixturenames <pytest.FixtureRequest.fixturenames>`) to omit fixtures that are requested transitively from overridden fixtures.

- [#&#8203;14263](https://redirect.github.com/pytest-dev/pytest/issues/14263): Unraisable exceptions from finalizers are now collected during `pytest_unconfigure`, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an active `error` filter could be removed before the exception surfaced and a late resource leak would pass silently. A `-W error` filter, or any filter matching `pytest.PytestUnraisableExceptionWarning`, now promotes these exceptions to failures regardless of plugin cleanup order.

- [#&#8203;14377](https://redirect.github.com/pytest-dev/pytest/issues/14377): Fixed crash in <span class="title-ref">Config.get\_terminal\_writer</span> when an assertion fails with the `terminalreporter` plugin disabled.

- [#&#8203;14381](https://redirect.github.com/pytest-dev/pytest/issues/14381): Fixed `-V` (short form of `--version`) to properly display the current version.

- [#&#8203;14389](https://redirect.github.com/pytest-dev/pytest/issues/14389): Improved `pytest.raises(..., match=...) <pytest.raises>` failures to suppress the mismatched exception as a cause of the resulting `AssertionError`.

- [#&#8203;14392](https://redirect.github.com/pytest-dev/pytest/issues/14392): Fixed a bug in `pytest.raises(match=...) <pytest.raises>` "fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead.

- [#&#8203;14442](https://redirect.github.com/pytest-dev/pytest/issues/14442): Fixed a regression in pytest 9.0 where `--strict-markers` and `--strict-config` specified through `addopts` were silently ignored.

  Note that when targeting pytest >= 9.0, it's nicer to use `strict_markers` and `strict_config`, or `strict mode <strict mode>`.

- [#&#8203;14456](https://redirect.github.com/pytest-dev/pytest/issues/14456): Fixed `pytest.approx` not recognizing types with `__array_interface__` as numpy-like arrays.

- [#&#8203;14474](https://redirect.github.com/pytest-dev/pytest/issues/14474): Fixed a regression where `-k` and `-m` expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a `SyntaxError` about escaping.

- [#&#8203;14483](https://redirect.github.com/pytest-dev/pytest/issues/14483): Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by `EternalRights`

- [#&#8203;14492](https://redirect.github.com/pytest-dev/pytest/issues/14492): Fixed `Code.getargs()` incorrectly including local variable names in the returned argument tuple for functions with `*args` and/or `**kwargs`. The method was using `co_flags` bitmask values (`4` and `8`) directly as counts instead of converting them to `1` via `bool()`, and was not accounting for `co_kwonlyargcount` when `var=True`.

- [#&#8203;3697](https://redirect.github.com/pytest-dev/pytest/issues/3697): Logging capture now works for non-propagating loggers.
  Previously only logs which reached the root logger were captured.
  This includes `caplog` and the "Captured log calls" test reporting.

- [#&#8203;3850](https://redirect.github.com/pytest-dev/pytest/issues/3850): Fixed JUnit XML report: the `tests` attribute of the `<testsuite>` element now always matches the number of `<testcase>` elements in the file. In some cases (test passes but fails during teardown) the `tests` attribute would report an incorrect number of testcases in the XML file.

- [#&#8203;5848](https://redirect.github.com/pytest-dev/pytest/issues/5848): `pytest_fixture_post_finalizer` is no longer called extra times for the same fixture teardown in some cases.

- [#&#8203;719](https://redirect.github.com/pytest-dev/pytest/issues/719): Fixed `@pytest.mark.parametrize <pytest.mark.parametrize ref>` not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g., `"arg,"`).

  The trailing comma form now correctly behaves like the tuple form `("arg",)`, treating argvalues as a list of tuples to unpack.

##### Improved documentation

- [#&#8203;11022](https://redirect.github.com/pytest-dev/pytest/issues/11022): Document safer alternatives and scope guidance for monkeypatching standard library functions.
- [#&#8203;11307](https://redirect.github.com/pytest-dev/pytest/issues/11307): Document that `@pytest.hookimpl(specname=...)` only works for function names starting with `pytest_`.
- [#&#8203;13038](https://redirect.github.com/pytest-dev/pytest/issues/13038): Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures.
- [#&#8203;13155](https://redirect.github.com/pytest-dev/pytest/issues/13155): Clarified how the `request` fixture provides indirect parametrization values via `request.param`.
- [#&#8203;13304](https://redirect.github.com/pytest-dev/pytest/issues/13304): Clarified in the documentation that hook implementations defined in `conftest.py` files are not available to other plugins during their `pytest_addoption()` execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement `pytest_addoption()` to add their own command-line options.
- [#&#8203;13902](https://redirect.github.com/pytest-dev/pytest/issues/13902): Clarified how subtest progress markers are shown in the documentation.
- [#&#8203;14012](https://redirect.github.com/pytest-dev/pytest/issues/14012): The `ini options ref` section of the API Reference now specified the type and default value of every configuration option.
- [#&#8203;14148](https://redirect.github.com/pytest-dev/pytest/issues/14148): Documented a safe `pytestconfig.cache` access pattern when the
  `cacheprovider` plugin is disabled.
- [#&#8203;14303](https://redirect.github.com/pytest-dev/pytest/issues/14303): The documentation is now built with Sphinx >= 9.
- [#&#8203;14465](https://redirect.github.com/pytest-dev/pytest/issues/14465): Updated the hooks how-to page to link the `newhooks.py` file in `pytest-xdist` at tag `v3.8.0` instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on.

##### Miscellaneous internal changes

- [#&#8203;14582](https://redirect.github.com/pytest-dev/pytest/issues/14582): Improved the recursion traceback test to exercise all requested traceback styles.

### [`v9.0.3`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.3)

[Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.2...9.0.3)

### pytest 9.0.3 (2026-04-07)

#### Bug fixes

- [#&#8203;12444](https://redirect.github.com/pytest-dev/pytest/issues/12444): Fixed `pytest.approx` which now correctly takes into account `~collections.abc.Mapping` keys order to compare them.

- [#&#8203;13634](https://redirect.github.com/pytest-dev/pytest/issues/13634): Blocking a `conftest.py` file using the `-p no:` option is now explicitly disallowed.

  Previously this resulted in an internal assertion failure during plugin loading.

  Pytest now raises a clear `UsageError` explaining that conftest files are not plugins and cannot be disabled via `-p`.

- [#&#8203;13734](https://redirect.github.com/pytest-dev/pytest/issues/13734): Fixed crash when a test raises an exceptiongroup with `__tracebackhide__ = True`.

- [#&#8203;14195](https://redirect.github.com/pytest-dev/pytest/issues/14195): Fixed an issue where non-string messages passed to <span class="title-ref">unittest.TestCase.subTest()</span> were not printed.

- [#&#8203;14343](https://redirect.github.com/pytest-dev/pytest/issues/14343): Fixed use of insecure temporary directory (CVE-2025-71176).

#### Improved documentation

- [#&#8203;13388](https://redirect.github.com/pytest-dev/pytest/issues/13388): Clarified documentation for `-p` vs `PYTEST_PLUGINS` plugin loading and fixed an incorrect `-p` example.
- [#&#8203;13731](https://redirect.github.com/pytest-dev/pytest/issues/13731): Clarified that capture fixtures (e.g. `capsys` and `capfd`) take precedence over the `-s` / `--capture=no` command-line options in `Accessing captured output from a test function <accessing-captured-output>`.
- [#&#8203;14088](https://redirect.github.com/pytest-dev/pytest/issues/14088): Clarified that the default `pytest_collection` hook sets `session.items` before it calls `pytest_collection_finish`, not after.
- [#&#8203;14255](https://redirect.github.com/pytest-dev/pytest/issues/14255): TOML integer log levels must be quoted: Updating reference documentation.

#### Contributor-facing changes

- [#&#8203;12689](https://redirect.github.com/pytest-dev/pytest/issues/12689): The test reports are now published to Codecov from GitHub Actions.
  The test statistics is visible [on the web interface](https://app.codecov.io/gh/pytest-dev/pytest/tests).

  \-- by `aleguy02`

### [`v9.0.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.2)

[Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.1...9.0.2)

### pytest 9.0.2 (2025-12-06)

#### Bug fixes

- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896): The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators.

  You may enable it again by passing `-p terminalprogress`. We may enable it by default again once compatibility improves in the future.

  Additionally, when the environment variable `TERM` is `dumb`, the escape codes are no longer emitted, even if the plugin is enabled.

- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904): Fixed the TOML type of the `tmp_path_retention_count` settings in the API reference from number to string.

- [#&#8203;13946](https://redirect.github.com/pytest-dev/pytest/issues/13946): The private `config.inicfg` attribute was changed in a breaking manner in pytest 9.0.0.
  Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim.
  It will be deprecated in pytest 9.1 and removed in pytest 10.

- [#&#8203;13965](https://redirect.github.com/pytest-dev/pytest/issues/13965): Fixed quadratic-time behavior when handling `unittest` subtests in Python 3.10.

#### Improved documentation

- [#&#8203;4492](https://redirect.github.com/pytest-dev/pytest/issues/4492): The API Reference now contains cross-reference-able documentation of `pytest's command-line flags <command-line-flags>`.

### [`v9.0.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.1)

[Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.0...9.0.1)

### pytest 9.0.1 (2025-11-12)

#### Bug fixes

- [#&#8203;13895](https://redirect.github.com/pytest-dev/pytest/issues/13895): Restore support for skipping tests via `raise unittest.SkipTest`.
- [#&#8203;13896](https://redirect.github.com/pytest-dev/pytest/issues/13896): The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.
- [#&#8203;13904](https://redirect.github.com/pytest-dev/pytest/issues/13904): Fixed the TOML type of the verbosity settings in the API reference from number to string.
- [#&#8203;13910](https://redirect.github.com/pytest-dev/pytest/issues/13910): Fixed <span class="title-ref">UserWarning: Do not expect file\_or\_dir</span> on some earlier Python 3.12 and 3.13 point versions.

#### Packaging updates and notes for downstreams

- [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933): The tox configuration has been adjusted to make sure the desired
  version string can be passed into its `package_env` through
  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment
  variable as a part of the release process -- by `webknjaz`.

#### Contributor-facing changes

- [#&#8203;13891](https://redirect.github.com/pytest-dev/pytest/issues/13891), [#&#8203;13942](https://redirect.github.com/pytest-dev/pytest/issues/13942): The CI/CD part of the release automation is now capable of
  creating GitHub Releases without having a Git checkout on
  disk -- by `bluetech` and `webknjaz`.
- [#&#8203;13933](https://redirect.github.com/pytest-dev/pytest/issues/13933): The tox configuration has been adjusted to make sure the desired
  version string can be passed into its `package_env` through
  the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment
  variable as a part of the release process -- by `webknjaz`.

### [`v9.0.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.0)

[Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.4.2...9.0.0)

### pytest 9.0.0 (2025-11-05)

#### New features

- [#&#8203;1367](https://redirect.github.com/pytest-dev/pytest/issues/1367): **Support for subtests** has been added.

  `subtests <subtests>` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

  Example:

  ```python
  def contains_docstring(p: Path) -> bool:
      """Return True if the given Python file contains a top-level docstring."""
      ...

  def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
      for path in Path.cwd().glob("*.py"):
          with subtests.test(path=str(path)):
              assert contains_docstring(path)
  ```

  Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

  In addition, `unittest.TestCase.subTest` is now also supported.

  This feature was originally implemented as a separate plugin in [pytest-subtests](https://redirect.github.com/pytest-dev/pytest-subtests), but since then has been merged into the core.

  > \[!NOTE]
  > This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.

- [#&#8203;13743](https://redirect.github.com/pytest-dev/pytest/issues/13743): Added support for **native TOML configuration files**.

  While pytest, since version 6, supports configuration in `pyproject.toml` files under `[tool.pytest.ini_options]`,
  it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings.
  Now, pytest supports the native TOML data model.

  In `pyproject.toml`, the native TOML configuration is under the `[tool.pytest]` table.

  ```toml
  # pyproject.toml
  [tool.pytest]
  minversion = "9.0"
  addopts = ["-ra", "-q"]
  testpaths = [
      "tests",
      "integration",
  ]
  ```

  The `[tool.pytest.ini_options]` table remains supported, but both tables cannot be used at the same time.

  If you prefer to use a separate configuration file, or don't use `pyproject.toml`, you can use `pytest.toml` or `.pytest.toml`:

  ```toml
  # pytest.toml or .pytest.toml
  [pytest]
  minversion = "9.0"
  addopts = ["-ra", "-q"]
  testpaths = [
      "tests",
      "integration",
  ]
  ```

  The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

  See `config file formats` for full details.

- [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823): Added a **"strict mode"** enabled by the `strict` configuration option.

  When set to `true`, the `strict` option currently enables

  - `strict_config`
  - `strict_markers`
  - `strict_parametrization_ids`
  - `strict_xfail`

  The individual strictness options can be explicitly set to override the global `strict` setting.

  The previously-deprecated `--strict` command-line flag now enables strict mode.

  If pytest adds new strictness options in the future, they will also be enabled in strict mode.
  Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
  or if you want to proactively adopt new strictness options as they are added.

  See `strict mode` for more details.

- [#&#8203;13737](https://redirect.github.com/pytest-dev/pytest/issues/13737): Added the `strict_parametrization_ids` configuration option.

  When set, pytest emits an error if it detects non-unique parameter set IDs,
  rather than automatically making the IDs unique by adding <span class="title-ref">0</span>, <span class="title-ref">1</span>, ... to them.
  This can be particularly useful for catching unintended duplicates.

- [#&#8203;13072](https://redirect.github.com/pytest-dev/pytest/issues/13072): Added support for displaying test session **progress in the terminal tab** using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC) ANSI sequence.
  When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
  you'll see the progress in the terminal tab or window,
  allowing you to monitor pytest's progress at a glance.

  This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:

  - On a user level, using `-p no:terminalprogress` on the command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`.
  - On a project configuration level, using `addopts = "-p no:terminalprogress"`.

- [#&#8203;478](https://redirect.github.com/pytest-dev/pytest/issues/478): Support PEP420 (implicit namespace packages) as <span class="title-ref">--pyargs</span> target when `consider_namespace_packages` is <span class="title-ref">true</span> in the config.

  Previously, this option only impacted package imports, now it also impacts tests discovery.

- [#&#8203;13678](https://redirect.github.com/pytest-dev/pytest/issues/13678): Added a new `faulthandler_exit_on_timeout` configuration option set to "false" by default to let <span class="title-ref">faulthandler</span> interrupt the <span class="title-ref">pytest</span> process after a timeout in case of deadlock.

  Previously, a <span class="title-ref">faulthandler</span> timeout would only dump the traceback of all threads to stderr, but would not interrupt the <span class="title-ref">pytest</span> process.

  \-- by `ogrisel`.

- [#&#8203;13829](https://redirect.github.com/pytest-dev/pytest/issues/13829): Added support for configuration option aliases via the `aliases` parameter in `Parser.addini() <pytest.Parser.addini>`.

  Plugins can now register alternative names for configuration options,
  allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
  The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.

#### Improvements in existing functionality

- [#&#8203;13330](https://redirect.github.com/pytest-dev/pytest/issues/13330): Having pytest configuration spread over more than one file (for example having both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]` table) will now print a warning to make it clearer to the user that only one of them is actually used.

  \-- by `sgaist`

- [#&#8203;13574](https://redirect.github.com/pytest-dev/pytest/issues/13574): The single argument `--version` no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

  Passing `--version` twice (e.g., `pytest --version --version`) retains the original behavior, showing both the pytest version and plugin information.

  > \[!NOTE]
  > Since `--version` is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`.

- [#&#8203;13823](https://redirect.github.com/pytest-dev/pytest/issues/13823): Added `strict_xfail` as an alias to the `xfail_strict` option,
  `strict_config` as an alias to the `--strict-config` flag,
  and `strict_markers` as an alias to the `--strict-markers` flag.
  This makes all strictness options consistently have configuration options with the prefix `strict_`.

- [#&#8203;13700](https://redirect.github.com/pytest-dev/pytest/issues/13700): <span class="title-ref">--junitxml</span> no longer prints the <span class="title-ref">generated xml file</span> summary at the end of the pytest session when <span class="title-ref">--quiet</span> is given.

- [#&#8203;13732](https://redirect.github.com/pytest-dev/pytest/issues/13732): Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.

- [#&#8203;13859](https://redirect.github.com/pytest-dev/pytest/issues/13859): Clarify the error message for <span class="title-ref">pytest.raises()</span> when a regex <span class="title-ref">match</span> fails.

- [#&#8203;13861](https://redirect.github.com/pytest-dev/pytest/issues/13861): Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be \<expected>, but got \<actual>". Now, it is "Expected \<expected>, but got \<actual>".

#### Removals and backward incompatible breaking changes

- [#&#8203;12083](https://redirect.github.com/pytest-dev/pytest/issues/12083): Fixed a bug where an invocation such as <span class="title-ref">pytest a/ a/b</span> would cause only tests from <span class="title-ref">a/b</span> to run, and not other tests under <span class="title-ref">a/</span>.

  The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

  1. <span class="title-ref">pytest a/b a/</span> or <span class="title-ref">pytest a/ a/b</span> are equivalent to <span class="title-ref">pytest a</span>; if an argument overlaps another arguments, only the prefix remains.
  2. <span class="title-ref">pytest x.py x.py</span> is equivalent to <span class="title-ref">pytest x.py</span>; previously such an invocation was taken as an explicit request to run the tests from the file twice.

  If you rely on these behaviors, consider using `--keep-duplicates <duplicate-paths>`, which retains its existing behavior (including the bug).

- [#&#8203;13719](https://redirect.github.com/pytest-dev/pytest/issues/13719): Support for Python 3.9 is dropped following its end of life.

- [#&#8203;13766](https://redirect.github.com/pytest-dev/pytest/issues/13766): Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables <span class="title-ref">$CI</span> or <span class="title-ref">$BUILD\_NUMBER</span> was defined;
  now, CI mode is only activated if at least one of those variables is defined and set to a *non-empty* value.

- [#&#8203;13779](https://redirect.github.com/pytest-dev/pytest/issues/13779): **PytestRemovedIn9Warning deprecation warnings are now errors by default.**

  Following our plan to remove deprecated features with as little disruption as
  possible, all warnings of type `PytestRemovedIn9Warning` now generate errors
  instead of warning messages by default.

  **The affected features will be effectively removed in pytest 9.1**, so please consult the
  `deprecations` section in the docs for directions on how to update existing code.

  In the pytest `9.0.X` series, it is possible to change the errors back into warnings as a
  stopgap measure by adding this to your `pytest.ini` file:

  ```ini
  [pytest]
  filterwarnings =
      ignore::pytest.PytestRemovedIn9Warning
  ```

  But this will stop working when pytest `9.1` is released.

  **If you have concerns** about the removal of a specific feature, please add a
  comment to `13779`.

#### Deprecations (removal in next major release)

- [#&#8203;13807](https://redirect.github.com/pytest-dev/pytest/issues/13807): `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now issues a deprecation warning when the prepended path contains legacy namespace packages (those using `pkg_resources.declare_namespace()`).
  Users should migrate to native namespace packages (`420`).
  See `monkeypatch-fixup-namespace-packages` for details.

#### Bug fixes

- [#&#8203;13445](https://redirect.github.com/pytest-dev/pytest/issues/13445): Made the type annotations of `pytest.skip` and friends more spec-complaint to have them work across more type checkers.

- [#&#8203;13537](https://redirect.github.com/pytest-dev/pytest/issues/13537): Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in teardown was not handled correctly and showed as error.

- [#&#8203;13598](https://redirect.github.com/pytest-dev/pytest/issues/13598): Fixed possible collection confusion on Windows when short paths and symlinks are involved.

- [#&#8203;13716](https://redirect.github.com/pytest-dev/pytest/issues/13716): Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file cannot be parametrized) was silently treated as `pytest x.py`. This is now a usage error.

- [#&#8203;13722](https://redirect.github.com/pytest-dev/pytest/issues/13722): Fixed a misleading assertion failure message when using `pytest.approx` on mappings with differing lengths.

- [#&#8203;13773](https://redirect.github.com/pytest-dev/pytest/issues/13773): Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.

- [#&#8203;13816](https://redirect.github.com/pytest-dev/pytest/issues/13816): Fixed `pytest.approx` which now returns a clearer error message when comparing mappings with different keys.

- [#&#8203;13849](https://redirect.github.com/pytest-dev/pytest/issues/13849): Hidden `.pytest.ini` files are now picked up as the config file even if empty.
  This was an inconsistency with non-hidden `pytest.ini`.

- [#&#8203;13865](https://redirect.github.com/pytest-dev/pytest/issues/13865): Fixed <span class="title-ref">--show-capture</span> with <span class="title-ref">--tb=line</span>.

- [#&#8203;13522](https://redirect.github.com/pytest-dev/pytest/issues/13522): Fixed `pytester` in subprocess mode ignored all :attr\`pytester.plugins \<pytest.Pytester.plugins>\` except the first.

  Fixed `pytester` in subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`.
  Now it errors instead.
  If you are affected by this, specify the plugin by name, or switch the affected tests to use `pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess>` explicitly instead.

#### Packaging updates and notes for downstreams

- [#&#8203;13791](https://redirect.github.com/pytest-dev/pytest/issues/13791): Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1` and `22.0.0`, respectively.

#### Contributor-facing changes

- [#&#8203;12244](https://redirect.github.com/pytest-dev/pytest/issues/12244): Fixed self-test failures when <span class="title-ref">TERM=dumb</span>.
- [#&#8203;12474](https://redirect.github.com/pytest-dev/pytest/issues/12474): Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation.
- [#&#8203;13621](https://redirect.github.com/pytest-dev/pytest/issues/13621): pytest's own testsuite now handles the `lsof` command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds.
- [#&#8203;13638](https://redirect.github.com/pytest-dev/pytest/issues/13638): Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`.
  The script now uses `gh pr create` which is compatible with GitHub CLI v2.0+.
- [#&#8203;13695](https://redirect.github.com/pytest-dev/pytest/issues/13695): Flush <span class="title-ref">stdout</span> and <span class="title-ref">stderr</span> in <span class="title-ref">Pytester.run</span> to avoid truncated outputs in <span class="title-ref">test\_faulthandler.py::test\_timeout</span> on CI -- by `ogrisel`.
- [#&#8203;13771](https://redirect.github.com/pytest-dev/pytest/issues/13771): Skip <span class="title-ref">test\_do\_not\_collect\_symlink\_siblings</span> on Windows environments without symlink support to avoid false negatives.
- [#&#8203;13841](https://redirect.github.com/pytest-dev/pytest/issues/13841): `tox>=4` is now required when contributing to pytest.
- [#&#8203;13625](https://redirect.github.com/pytest-dev/pytest/issues/13625): Added missing docstrings to `pytest_addoption()`, `pytest_configure()`, and `cacheshow()` functions in `cacheprovider.py`.

#### Miscellaneous internal changes

- [#&#8203;13830](https://redirect.github.com/pytest-dev/pytest/issues/13830): Configuration overrides (`-o`/`--override-ini`) are now processed during startup rather than during `config.getini() <pytest.Config.getini>`.

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/osism/ansible-collection-services).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->

      patchset: db85d442c9f545811efe766d1b18b2a74c53c358
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 3d5c7b5973754999f7005857a00ce9168944f0f1
          trusted/project_1/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 038dd8b856c62af4433c8477c5cb3d0480847059
          trusted/project_2/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: 0c74c57cedff2b36bb37ca68a5338d1c49991496
          untrusted/project_0/github.com/osism/zuul-jobs:
            canonical_name: github.com/osism/zuul-jobs
            checkout: main
            commit: 0c74c57cedff2b36bb37ca68a5338d1c49991496
          untrusted/project_1/github.com/osism/zuul-config:
            canonical_name: github.com/osism/zuul-config
            checkout: main
            commit: 3d5c7b5973754999f7005857a00ce9168944f0f1
          untrusted/project_2/github.com/osism/openinfra-zuul-jobs:
            canonical_name: github.com/osism/openinfra-zuul-jobs
            checkout: master
            commit: 038dd8b856c62af4433c8477c5cb3d0480847059
        playbooks:
        - path: untrusted/project_0/github.com/osism/zuul-jobs/playbooks/flake8/run.yaml
          roles:
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/playbook_0/role_0/zuul-config
            link_target: untrusted/project_1/github.com/osism/zuul-config
            role_path: ansible/playbook_0/role_0/zuul-config/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/playbook_0/role_1/openinfra-zuul-jobs
            link_target: untrusted/project_2/github.com/osism/openinfra-zuul-jobs
            role_path: ansible/playbook_0/role_1/openinfra-zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/osism/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
      post_review: false
      post_timeout: 1800
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/osism/ansible-collection-services
        name: osism/ansible-collection-services
        short_name: ansible-collection-services
        src_dir: src/github.com/osism/ansible-collection-services
      projects:
        github.com/osism/ansible-collection-services:
          canonical_hostname: github.com
          canonical_name: github.com/osism/ansible-collection-services
          checkout: main
          checkout_description: zuul branch
          commit: 85d70a6486e7fdcf0f8983a0f43103e33dd84b7b
          name: osism/ansible-collection-services
          required: false
          short_name: ansible-collection-services
          src_dir: src/github.com/osism/ansible-collection-services
      ref: refs/pull/2103/head
      resources: {}
      tenant: osism
      timeout: 1800
      topic: null
      voting: true
