FAQ | This is a LIVE service | Changelog

fix(deps): update all non-major dependencies

uis-devops-renovatebotrequested to merge
renovate/all-minor-patch into master

This MR contains the following updates:

Package Type Update Change
coverage dev minor 7.6.12 -> 7.9.1
faker (changelog) dependencies minor 37.0.0 -> 37.4.0
google-auth dependencies minor 2.38.0 -> 2.40.3
google-cloud-kms (source) dependencies minor 3.4.0 -> 3.5.1
google-cloud-secret-manager (source) dependencies minor 2.23.1 -> 2.24.0
pre-commit dev minor 4.1.0 -> 4.2.0
pre-commit/mirrors-mypy repository minor v1.15.0 -> v1.16.1
pycqa/flake8 repository minor 7.1.1 -> 7.2.0
pydantic (changelog) dependencies minor 2.10.6 -> 2.11.7
pydantic-settings (changelog) dependencies minor 2.8.1 -> 2.9.1
pytest (changelog) dev minor 8.3.5 -> 8.4.1
pytest-cov (changelog) dev minor 6.0.0 -> 6.2.1
pytest-mock (changelog) dev patch 3.14.0 -> 3.14.1
structlog (changelog) dependencies minor 25.2.0 -> 25.4.0
timothycrosley/isort repository patch 6.0.0 -> 6.0.1
uis/devops/continuous-delivery/ci-templates repository minor v6.5.0 -> v6.15.0

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

Release Notes

nedbat/coveragepy (coverage)

v7.9.1

Compare Source

  • The "no-ctracer" warning is not issued for Python pre-release versions. Coverage doesn't ship compiled wheels for those versions, so this was far too noisy.

  • On Python 3.14+, the "sysmon" core is now the default if it's supported for your configuration. Plugins and dynamic contexts are still not supported with it.

.. _changes_7-9-0:

v7.9.0

Compare Source

  • Added a [run] core configuration setting to specify the measurement core, which was previously only available through the COVERAGE_CORE environment variable. Finishes issue 1746_.

  • Fixed incorrect rendering of f-strings with doubled braces, closing issue 1980_.

  • If the C tracer core can't be imported, a warning ("no-ctracer") is issued with the reason.

  • The C tracer core extension module now conforms to PEP 489, closing issue 1977. Thanks, Adam Turner <pull 1978_>_.

  • Fixed a "ValueError: min() arg is an empty sequence" error caused by strange empty modules, found by oss-fuzz_.

.. _issue 1746: https://github.com/nedbat/coveragepy/issues/1746 .. _issue 1977: https://github.com/nedbat/coveragepy/issues/1977 .. _pull 1978: https://github.com/nedbat/coveragepy/pull/1978 .. _issue 1980: https://github.com/nedbat/coveragepy/issues/1980 .. _PEP 489: https://peps.python.org/pep-0489 .. _oss-fuzz: https://google.github.io/oss-fuzz/

.. _changes_7-8-2:

v7.8.2

Compare Source

  • Wheels are provided for Windows ARM64 on Python 3.11, 3.12, and 3.13. Thanks, Finn Womack <pull 1972_>_.

.. _issue 1971: https://github.com/nedbat/coveragepy/pull/1971 .. _pull 1972: https://github.com/nedbat/coveragepy/pull/1972

.. _changes_7-8-1:

v7.8.1

Compare Source

  • A number of EncodingWarnings were fixed that could appear if you've enabled PYTHONWARNDEFAULTENCODING, fixing issue 1966. Thanks, Henry Schreiner <pull 1967_>.

  • Fixed a race condition when using sys.monitoring with free-threading Python, closing issue 1970_.

.. _issue 1966: https://github.com/nedbat/coveragepy/issues/1966 .. _pull 1967: https://github.com/nedbat/coveragepy/pull/1967 .. _issue 1970: https://github.com/nedbat/coveragepy/issues/1970

.. _changes_7-8-0:

v7.8.0

Compare Source

  • Added a new source_dirs setting for symmetry with the existing source_pkgs setting. It's preferable to the existing source setting, because you'll get a clear error when directories don't exist. Fixes issue 1942. Thanks, Jeremy Fleischman <pull 1943_>.

  • Fix: the PYTHONSAFEPATH environment variable new in Python 3.11 is properly supported, closing issue 1696. Thanks, Philipp A. <pull 1700_>. This works properly except for a detail when using the coverage command on Windows. There you can use python -m coverage instead if you need exact emulation.

.. _issue 1696: https://github.com/nedbat/coveragepy/issues/1696 .. _pull 1700: https://github.com/nedbat/coveragepy/pull/1700 .. _issue 1942: https://github.com/nedbat/coveragepy/issues/1942 .. _pull 1943: https://github.com/nedbat/coveragepy/pull/1943

.. _changes_7-7-1:

v7.7.1

Compare Source

  • A few small tweaks to the sys.monitoring support for Python 3.14. Please test!

.. _changes_7-7-0:

v7.7.0

Compare Source

  • The Coverage object has a new method, :meth:.Coverage.branch_stats for getting simple branch information for a module. Closes issue 1888_.

  • The :class:Coverage constructor<.Coverage> now has a plugins parameter for passing in plugin objects directly, thanks to Alex Gaynor <pull 1919_>_.

  • Many constant tests in if statements are now recognized as being optimized away. For example, previously if 13: would have been considered a branch with one path not taken. Now it is understood as always true and no coverage is missing.

  • The experimental sys.monitoring support now works for branch coverage if you are using Python 3.14.0 alpha 6 or newer. This should reduce the overhead coverage.py imposes on your test suite. Set the environment variable COVERAGE_CORE=sysmon to try it out.

  • Confirmed support for PyPy 3.11. Thanks Michał Górny.

.. _issue 1888: https://github.com/nedbat/coveragepy/issues/1888 .. _pull 1919: https://github.com/nedbat/coveragepy/pull/1919

.. _changes_7-6-12:

joke2k/faker (faker)

v37.4.0

Compare Source

v37.3.0

Compare Source

v37.2.1

Compare Source

  • Remove duplicate cities in de_DE address provider. Thanks @​KarelZe.

v37.2.0

Compare Source

v37.1.1

Compare Source

  • Fix type annotations for Python 3.14. Thanks @​mgorny.

v37.1.0

Compare Source

v37.0.2

Compare Source

  • Fix type annotiation

v37.0.1

Compare Source

googleapis/google-auth-library-python (google-auth)

v2.40.3

Compare Source

Bug Fixes

v2.40.2

Compare Source

Bug Fixes
  • Remove sync response logs in AuthorizedSession (97ed1c8)
  • Update test to consider new error message from cryptography (#​1765) (44e38b6)

v2.40.1

Compare Source

Bug Fixes

v2.40.0

Compare Source

Features
Bug Fixes
  • Correct webauthn JSON parsing to be compliant with standard. (#​1658) (0c5ef36)

v2.39.0

Compare Source

Features
  • Adds GA support for X.509 workload identity federation (#​1695) (7495960)
Bug Fixes
googleapis/google-cloud-python (google-cloud-kms)

v3.5.1: google-cloud-kms: v3.5.1

Compare Source

Documentation
  • [google-cloud-kms] A comment for enum value DESTROYED in enum CryptoKeyVersionState is changed (#​13913) (cdca657)

v3.5.0: google-cloud-kms: v3.5.0

Compare Source

Features
  • Adding eTag field to AutokeyConfig (5d7b972)
Documentation
  • Updating docs for total_size field in KMS List APIs (5d7b972)

v3.4.1

Compare Source

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

v4.2.0

Compare Source

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

Features
  • For language: python first attempt a versioned python executable for the default language version before consulting a potentially unversioned sys.executable.
Fixes
pre-commit/mirrors-mypy (pre-commit/mirrors-mypy)

v1.16.1

Compare Source

v1.16.0

Compare Source

pycqa/flake8 (pycqa/flake8)

v7.2.0

Compare Source

v7.1.2

Compare Source

pydantic/pydantic (pydantic)

v2.11.7

Compare Source

GitHub release

What's Changed
Fixes

v2.11.6

Compare Source

GitHub release

What's Changed
Fixes

v2.11.5

Compare Source

GitHub release

What's Changed
Fixes

v2.11.4

Compare Source

GitHub release

What's Changed
Packaging
Changes
  • Allow config and bases to be specified together in create_model() by @​Viicos in #​11714. This change was backported as it was previously possible (although not meant to be supported) to provide model_config as a field, which would make it possible to provide both configuration and bases.
Fixes

v2.11.3

Compare Source

GitHub release

What's Changed
Packaging
Fixes

v2.11.2

Compare Source

GitHub release

What's Changed
Fixes

v2.11.1

Compare Source

GitHub release

What's Changed
Fixes
  • Do not override 'definitions-ref' schemas containing serialization schemas or metadata by @​Viicos in #​11644

v2.11.0

Compare Source

GitHub release

What's Changed

Pydantic v2.11 is a version strongly focused on build time performance of Pydantic models (and core schema generation in general). See the blog post for more details.

Packaging
New Features
Fixes
  • Allow generic typed dictionaries to be used for unpacked variadic keyword parameters by @​Viicos in #​11571
  • Fix runtime error when computing model string representation involving cached properties and self-referenced models by @​Viicos in #​11579
  • Preserve other steps when using the ellipsis in the pipeline API by @​Viicos in #​11626
  • Fix deferred discriminator application logic by @​Viicos in #​11591
New Contributors
pydantic/pydantic-settings (pydantic-settings)

v2.9.1

Compare Source

v2.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/pydantic/pydantic-settings/compare/v2.8.1...v2.9.0

pytest-dev/pytest (pytest)

v8.4.1

Compare Source

pytest 8.4.1 (2025-06-17)

Bug fixes

  • #​13461: Corrected _pytest.terminal.TerminalReporter.isatty to support being called as a method. Before it was just a boolean which could break correct code when using -o log_cli=true).

  • #​13477: Reintroduced pytest.PytestReturnNotNoneWarning{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.

    This warning is raised when a test functions returns a value other than None, which is often a mistake made by beginners.

    See return-not-none{.interpreted-text role="ref"} for more information.

  • #​13497: Fixed compatibility with Twisted 25+.

Improved documentation

  • #​13492: Fixed outdated warning about faulthandler not working on Windows.

v8.4.0

Compare Source

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

  • #​11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.

  • #​12346: Tests will now fail, instead of raising a warning, if they return any value other than None.

  • #​12874: We dropped support for Python 3.8 following its end of life (2024-10-07).

  • #​12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.

    See the docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.

Deprecations (removal in next major release)

  • #​10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or autouse=True. For guidance on how to work around this warning see sync-test-async-fixture{.interpreted-text role="ref"}.

New features

  • #​11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.

  • #​12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.

  • #​12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.

  • #​12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.

    This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.

  • #​12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.

    For example:

contents of src/domain.py

class Testament: ...

contents of tests/test_testament.py

from domain import Testament

def test_testament(): ...
```

In this scenario with the default options, pytest will collect the class [Testament]{.title-ref} from [tests/test_testament.py]{.title-ref} because it starts with [Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace.

This behavior can now be prevented by setting the new `collect_imported_tests`{.interpreted-text role="confval"} configuration option to `false`, which will make pytest collect classes/functions from test files **only** if they are defined in that file.

\-- by `FreerGit`{.interpreted-text role="user"}

  • #​12765: Thresholds to trigger snippet truncation can now be set with truncation_limit_lines{.interpreted-text role="confval"} and truncation_limit_chars{.interpreted-text role="confval"}.

    See truncation-params{.interpreted-text role="ref"} for more information.

  • #​13125: console_output_style{.interpreted-text role="confval"} now supports times to show execution time of each test.

  • #​13192: pytest.raises{.interpreted-text role="func"} will now raise a warning when passing an empty string to match, as this will match against any value. Use match="^$" if you want to check that an exception has no message.

  • #​13192: pytest.raises{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has ^ and $ and is otherwise escaped.

  • #​13192: You can now pass with pytest.raises(check=fn): <pytest.raises>{.interpreted-text role="func"}, where fn is a function which takes a raised exception and returns a boolean. The raises fails if no exception was raised (as usual), passes if an exception is raised and fn returns True (as well as match and the type matching, if specified, which are checked before), and propagates the exception if fn returns False (which likely also fails the test).

  • #​13228: hidden-param{.interpreted-text role="ref"} can now be used in id of pytest.param{.interpreted-text role="func"} or in ids of Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"}. It hides the parameter set from the test name.

  • #​13253: New flag: --disable-plugin-autoload <disable_plugin_autoload>{.interpreted-text role="ref"} which works as an alternative to PYTEST_DISABLE_PLUGIN_AUTOLOAD{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files with addopts{.interpreted-text role="confval"}.

Improvements in existing functionality

  • #​10224: pytest's short and long traceback styles (how-to-modifying-python-tb-printing{.interpreted-text role="ref"}) now have partial 657{.interpreted-text role="pep"} support and will show specific code segments in the traceback.

    ================================= FAILURES =================================
_______________________ test_gets_correct_tracebacks _______________________

test_tracebacks.py:12: in test_gets_correct_tracebacks
    assert manhattan_distance(p1, p2) == 1
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
test_tracebacks.py:6: in manhattan_distance
    return abs(point_1.x - point_2.x) + abs(point_1.y - point_2.y)
                           ^^^^^^^^^
E   AttributeError: 'NoneType' object has no attribute 'x'

    -- by ammaraskar{.interpreted-text role="user"}

  • #​11118: Now pythonpath{.interpreted-text role="confval"} configures [$PYTHONPATH]{.title-ref} earlier than before during the initialization process, which now also affects plugins loaded via the [-p]{.title-ref} command-line option.

    -- by millerdev{.interpreted-text role="user"}

  • #​11381: The type parameter of the parser.addini method now accepts ["int"]{.title-ref} and "float" parameters, facilitating the parsing of configuration values in the configuration file.

    Example:

    def pytest_addoption(parser):
    parser.addini("int_value", type="int", default=2, help="my int value")
    parser.addini("float_value", type="float", default=4.2, help="my float value")

    The [pytest.ini]{.title-ref} file:

    [pytest]
int_value = 3
float_value = 5.4

  • #​11525: Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function.

    -- by the-compiler{.interpreted-text role="user"} and glyphack{.interpreted-text role="user"}

  • #​12426: A warning is now issued when pytest.mark.usefixtures ref{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.

  • #​12707: Exception chains can be navigated when dropped into Pdb in Python 3.13+.

  • #​12736: Added a new attribute [name]{.title-ref} with the fixed value ["pytest tests"]{.title-ref} to the root tag [testsuites]{.title-ref} of the junit-xml generated by pytest.

    This attribute is part of many junit-xml specifications and is even part of the [junit-10.xsd]{.title-ref} specification that pytest's implementation is based on.

  • #​12943: If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info.

  • #​12958: A number of unraisable <unraisable>{.interpreted-text role="ref"} enhancements:

    • Set the unraisable hook as early as possible and unset it as late as possible, to collect the most possible number of unraisable exceptions.
    • Call the garbage collector just before unsetting the unraisable hook, to collect any straggling exceptions.
    • Collect multiple unraisable exceptions per test phase.
    • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
    • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
    • Report the unraisable exception as the cause of the pytest.PytestUnraisableExceptionWarning{.interpreted-text role="class"} exception if raised.
    • Compute the repr of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object.

  • #​13010: pytest.approx{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed.

  • #​13016: A number of threadexception <unraisable>{.interpreted-text role="ref"} enhancements:

    • Set the excepthook as early as possible and unset it as late as possible, to collect the most possible number of unhandled exceptions from threads.
    • Collect multiple thread exceptions per test phase.
    • Report the tracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
    • Avoid using a generator based hook to allow handling StopIteration{.interpreted-text role="class"} in test failures.
    • Report the thread exception as the cause of the pytest.PytestUnhandledThreadExceptionWarning{.interpreted-text role="class"} exception if raised.
    • Extract the name of the thread object in the excepthook which should help with resurrection of the thread.

  • #​13031: An empty parameter set as in pytest.mark.parametrize([], ids=idfunc) will no longer trigger a call to idfunc with internal objects.

  • #​13115: Allows supplying ExceptionGroup[Exception] and BaseExceptionGroup[BaseException] to pytest.raises to keep full typing on ExceptionInfo <pytest.ExceptionInfo>{.interpreted-text role="class"}:

    with pytest.raises(ExceptionGroup[Exception]) as exc_info:
    some_function()

    Parametrizing with other exception types remains an error - we do not check the types of child exceptions and thus do not permit code that might look like we do.

  • #​13122: The --stepwise mode received a number of improvements:

    • It no longer forgets the last failed test in case pytest is executed later without the flag.

      This enables the following workflow:

      1. Execute pytest with --stepwise, pytest then stops at the first failing test;
      2. Iteratively update the code and run the test in isolation, without the --stepwise flag (for example in an IDE), until it is fixed.
      3. Execute pytest with --stepwise again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests.

      Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test.

      This change however might cause issues if the --stepwise mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future).

    • New --stepwise-reset/--sw-reset flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning.

  • #​13308: Added official support for Python 3.14.

  • #​13380: Fix ExceptionGroup{.interpreted-text role="class"} traceback filtering to exclude pytest internals.

  • #​13415: The author metadata of the BibTex example is now correctly formatted with last names following first names. An example of BibLaTex has been added. BibTex and BibLaTex examples now clearly indicate that what is cited is software.

    -- by willynilly{.interpreted-text role="user"}

  • #​13420: Improved test collection performance by optimizing path resolution used in FSCollector.

  • #​13457: The error message about duplicate parametrization no longer displays an internal stack trace.

  • #​4112: Using pytest.mark.usefixtures <pytest.mark.usefixtures ref>{.interpreted-text role="ref"} on pytest.param{.interpreted-text role="func"} now produces an error instead of silently doing nothing.

  • #​5473: Replace [:]{.title-ref} with [;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling pytest.main{.interpreted-text role="func"}.

[#&#8203;6985](https://github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000.

:   -   The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results.

    -   Previously, the output for those ranges of values and tolerances was displayed in scientific notation (e.g., [42 ± 1.0e+00]{.title-ref}). The updated method now presents the tolerance as a decimal for better readability (e.g., [42 ± 1]{.title-ref}).

        Example:

        **Previous Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1.0e+00
        ```

        **Current Output:**

        ``` console
        >>> pytest.approx(42, abs=1)
        42 ± 1
        ```

    \-- by `fazeelghafoor`{.interpreted-text role="user"}
  • #​7683: The formerly optional pygments dependency is now required, causing output always to be source-highlighted (unless disabled via the --code-highlight=no CLI option).

Bug fixes

  • #​10404: Apply filterwarnings from config/cli as soon as possible, and revert them as late as possible so that warnings as errors are collected throughout the pytest run and before the unraisable and threadexcept hooks are removed.

    This allows very late warnings and unraisable/threadexcept exceptions to fail the test suite.

    This also changes the warning that the lsof plugin issues from PytestWarning to the new warning PytestFDWarning so it can be more easily filtered.

  • #​11067: The test report is now consistent regardless if the test xfailed via pytest.mark.xfail <pytest.mark.xfail ref>{.interpreted-text role="ref"} or pytest.fail{.interpreted-text role="func"}.

    Previously, xfailed tests via the marker would have the string "reason: " prefixed to the message, while those xfailed via the function did not. The prefix has been removed.

  • #​12008: In 11220{.interpreted-text role="pr"}, an unintended change in reordering was introduced by changing the way indices were assigned to direct params. More specifically, before that change, the indices of direct params to metafunc's callspecs were assigned after all parametrizations took place. Now, that change is reverted.

  • #​12863: Fix applying markers, including pytest.mark.parametrize <pytest.mark.parametrize ref>{.interpreted-text role="ref"} when placed above [@​staticmethod]{.title-ref} or [@​classmethod]{.title-ref}.

  • #​12929: Handle StopIteration from test cases, setup and teardown correctly.

  • #​12938: Fixed --durations-min argument not respected if -vv is used.

  • #​12946: Fixed missing help for pdb{.interpreted-text role="mod"} commands wrapped by pytest -- by adamchainz{.interpreted-text role="user"}.

  • #​12981: Prevent exceptions in pytest.Config.add_cleanup{.interpreted-text role="func"} callbacks preventing further cleanups.

  • #​13047: Restore pytest.approx{.interpreted-text role="func"} handling of equality checks between [bool]{.title-ref} and [numpy.bool_]{.title-ref} types.

    Comparing [bool]{.title-ref} and [numpy.bool_]{.title-ref} using pytest.approx{.interpreted-text role="func"} accidentally changed in version [8.3.4]{.title-ref} and [8.3.5]{.title-ref} to no longer match:

    >>> import numpy as np
>>> from pytest import approx
>>> [np.True_, np.True_] == pytest.approx([True, True])
False

    This has now been fixed:

    >>> [np.True_, np.True_] == pytest.approx([True, True])
True

  • #​13119: Improved handling of invalid regex patterns for filter warnings by providing a clear error message.

  • #​13175: The diff is now also highlighted correctly when comparing two strings.

  • #​13248: Fixed an issue where passing a scope in Metafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"} with indirect=True could result in other fixtures being unable to depend on the parametrized fixture.

  • #​13291: Fixed repr of attrs objects in assertion failure messages when using attrs>=25.2.

  • #​13312: Fixed a possible KeyError crash on PyPy during collection of tests involving higher-scoped parameters.

  • #​13345: Fix type hints for pytest.TestReport.when{.interpreted-text role="attr"} and pytest.TestReport.location{.interpreted-text role="attr"}.

  • #​13377: Fixed handling of test methods with positional-only parameter syntax.

    Now, methods are supported that formally define self as positional-only and/or fixture parameters as keyword-only, e.g.:

    class TestClass:

    def test_method(self, /, *, fixture): ...

    Before, this caused an internal error in pytest.

  • #​13384: Fixed an issue where pytest could report negative durations.

  • #​13420: Added lru_cache to nodes._check_initialpaths_for_relpath.

  • #​9037: Honor disable_test_id_escaping_and_forfeit_all_rights_to_community_support{.interpreted-text role="confval"} when escaping ids in parametrized tests.

Improved documentation

  • #​12535: [This example]{.title-ref}<https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures> showed print statements that do not exactly reflect what the different branches actually do. The fix makes the example more precise.

  • #​13218: Pointed out in the pytest.approx{.interpreted-text role="func"} documentation that it considers booleans unequal to numeric zero or one.

  • #​13221: Improved grouping of CLI options in the --help output.

  • #​6649: Added ~pytest.TerminalReporter{.interpreted-text role="class"} to the api-reference{.interpreted-text role="ref"} documentation page.

  • #​8612: Add a recipe for handling abstract test classes in the documentation.

    A new example has been added to the documentation to demonstrate how to use a mixin class to handle abstract test classes without manually setting the __test__ attribute for subclasses. This ensures that subclasses of abstract test classes are automatically collected by pytest.

Packaging updates and notes for downstreams

  • #​13317: Specified minimum allowed versions of colorama, iniconfig, and packaging; and bumped the minimum allowed version of exceptiongroup for python_version<'3.11' from a release candidate to a full release.

Contributor-facing changes

  • #​12017: Mixed internal improvements:

    • Migrate formatting to f-strings in some tests.
    • Use type-safe constructs in JUnitXML tests.
    • MovedMockTiming into _pytest.timing.

    -- by RonnyPfannschmidt{.interpreted-text role="user"}

  • #​12647: Fixed running the test suite with the hypothesis pytest plugin.

Miscellaneous internal changes

  • #​6649: Added ~pytest.TerminalReporter{.interpreted-text role="class"} to the public pytest API, as it is part of the signature of the pytest_terminal_summary{.interpreted-text role="hook"} hook.
pytest-dev/pytest-cov (pytest-cov)

v6.2.1

Compare Source

  • Added a version requirement for pytest's pluggy dependency (1.2.0, released 2023-06-21) that has the required new-style hookwrapper API.

  • Removed deprecated license classifier (packaging).

  • Disabled coverage warnings in two more situations where they have no value:

    • "module-not-measured" in workers
    • "already-imported" in subprocesses

v6.2.0

Compare Source

  • The plugin now adds 3 rules in the filter warnings configuration to prevent common coverage warnings being raised as obscure errors::

    default:unclosed database in <sqlite3.Connection object at:ResourceWarning once::PytestCovWarning once::CoverageWarning

    This fixes most of the bad interactions that are occurring on pytest 8.4 with filterwarnings=error.

    The plugin will check if there already matching rules for the 3 categories (ResourceWarning, PytestCovWarning, CoverageWarning) and message (unclosed database in <sqlite3.Connection object at) before adding the filters.

    This means you can have this in your pytest configuration for complete oblivion (not recommended, if that is not clear)::

    filterwarnings = [ "error", "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning", "ignore::PytestCovWarning", "ignore::CoverageWarning", ]

v6.1.1

Compare Source

  • Fixed breakage that occurs when --cov-context and the no_cover marker are used together.

v6.1.0

Compare Source

  • Change terminal output to use full width lines for the coverage header. Contributed by Tsvika Shapira in #&#8203;678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.
  • Removed unnecessary CovFailUnderWarning. Fixes #&#8203;675 <https://github.com/pytest-dev/pytest-cov/issues/675>_.
  • Fixed the term report not using the precision specified via --cov-precision.
pytest-dev/pytest-mock (pytest-mock)

v3.14.1

Compare Source

  • #&#8203;503 <https://github.com/pytest-dev/pytest-mock/pull/503>_: Python 3.14 is now officially supported.
hynek/structlog (structlog)

v25.4.0

Compare Source

Added

  • Support for Python 3.14 and Python 3.13.4.

    Python 3.14 has an backwards-incompatible change to logging.Logger.isEnabledFor() (it now always returns False if a log entry is in flight) that has been backported to 3.13.4 (expected on 2025-06-03). It mainly affects structlog.stdlib.filter_by_level(). #​723

  • structlog.tracebacks now handles exception groups. structlog.tracebacks.Stack has two new fields, is_group: bool and exceptions: list[Trace]. This works similarly to what Rich v14.0.0 does. #​720

Fixed
  • structlog.processors.ExceptionPrettyPrinter now respects the exception_formatter arguments instead of always using the default formatter. #​724

v25.3.0

Compare Source

Fixed
  • structlog.processors.TimeStamper now again uses timestamps using UTC for custom format strings when utc=True. #​713
timothycrosley/isort (timothycrosley/isort)

v6.0.1

Compare Source

Changes

🐞 Fixes

👷 Continuous Integration

uis/devops/continuous-delivery/ci-templates (uis/devops/continuous-delivery/ci-templates)

v6.15.0

Compare Source

Changed
  • terraform-module.yml: Add support for Terraform testing with additional cleanup scripts.
Fixed
  • terraform-module.yml: Override the tflint job so that the terraform_standard_module_structure rule is applied.
  • terraform-module.yml: Override the pre-commit job to avoid duplication of our terraform-fmt, tflint, and trivy jobs.

v6.14.2

Compare Source

v6.14.1

Compare Source

v6.14.0

Compare Source

v6.13.0

Compare Source

v6.12.3

Compare Source

v6.12.2

Compare Source

Fixed
  • terraform-module: override .test-job-rules from terraform-lint.yml as the terraform-module.yml template needs to support Auto-DevOps.

v6.12.1

Compare Source

v6.12.0

Compare Source

v6.11.0

Compare Source

Changed
  • terraform-lint: use custom tflint docker image for the tflint job. This image includes the UIS DevOps custom tflint ruleset.
  • terraform-lint: move default tflint arguments to a $TFLINT_ARGS variable to allow repositories to override if required.
  • terraform-module: enable tflint in our Terraform reusable module pipeline.

v6.10.0

Compare Source

Fixed
  • terraform-pipeline: Partially revert changes made in v5.1.0.
    • Plan jobs for branch push pipelines will be reverted.
    • Manual apply jobs for the development environment will remain in the merge request pipelines.

v6.9.0

Compare Source

v6.8.1

Compare Source

v6.8.0

Compare Source

v6.7.3

Compare Source

v6.7.2

Compare Source

v6.7.1

Compare Source

v6.7.0

Compare Source

v6.6.1

Compare Source

v6.6.0

Compare Source

Configuration

📅 Schedule: Branch creation - Monday through Friday ( * * * * 1-5 ) in timezone Europe/London, Automerge - At any time (no schedule defined).

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

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

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited by uis-devops-renovatebot

Merge request reports