FAQ | This is a LIVE service | Changelog

Skip to content

fix(deps): update all non-major dependencies

This MR contains the following updates:

Package Type Update Change Age Confidence
DavidAnson/markdownlint-cli2 repository minor v0.17.2 -> v0.19.1 age confidence
alessandrojcm/commitlint-pre-commit-hook repository minor v9.22.0 -> v9.23.0 age confidence
coverage dev minor 7.11.0 -> 7.12.0 age confidence
editorconfig-checker/editorconfig-checker.python repository minor 3.2.1 -> 3.5.0 age confidence
geddit dependencies patch 2.1.0 -> 2.1.1 age confidence
google-auth dependencies minor 2.40.1 -> 2.43.0 age confidence
google-cloud-pubsub dependencies minor 2.31.1 -> 2.33.0 age confidence
message-schemas dependencies minor ^0.6.0 -> ^0.7.0 age confidence
msgraph-sdk dependencies minor 1.28.0 -> 1.49.0 age confidence
pre-commit dev minor 4.3.0 -> 4.5.0 age confidence
pre-commit/mirrors-mypy repository minor v1.15.0 -> v1.18.2 age confidence
psf/black repository minor 25.9.0 -> 25.11.0 age confidence
pydantic (changelog) dependencies minor 2.11.7 -> 2.12.4 age confidence
pydantic-settings (changelog) dependencies minor 2.9.1 -> 2.12.0 age confidence
pytest (changelog) dev minor 8.3.5 -> 8.4.2 age confidence
pytest-env dev minor 1.1.5 -> 1.2.0 age confidence
registry.gitlab.developers.cam.ac.uk/uis/devops/lib/ucam-faas-python final minor 0.8.0 -> 0.17.5 age confidence
ucam-faas dependencies minor ^0.8.0 -> ^0.17.0 age confidence
ucam-observe dependencies patch 0.2.0 -> 0.2.2 age confidence
uis/devops/continuous-delivery/ci-templates repository minor v6.10.0 -> v6.15.0 age confidence

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

DavidAnson/markdownlint-cli2 (DavidAnson/markdownlint-cli2)

v0.19.1

Compare Source

v0.19.0

Compare Source

v0.18.1

Compare Source

v0.18.0

Compare Source

alessandrojcm/commitlint-pre-commit-hook (alessandrojcm/commitlint-pre-commit-hook)

v9.23.0

Compare Source

Features
  • bump the commitlint group with 2 updates (c395a79)
  • bump the commitlint group with 2 updates (2be08da)
  • bump the commitlint group with 2 updates (c3bd3f3)
coveragepy/coveragepy (coverage)

v7.12.0

Compare Source

  • The HTML report now shows separate coverage totals for statements and branches, as well as the usual combined coverage percentage. Thanks to Ryuta Otsuka for the discussion <issue 2081_>_ and the implementation <pull 2085_>_.

  • The JSON report now includes separate coverage totals for statements and branches, thanks to Ryuta Otsuka <pull 2090_>_.

  • Fix: except* clauses were not handled properly under the "sysmon" measurement core, causing KeyError exceptions as described in issue 2086_. This is now fixed.

  • Fix: we now defend against aggressive mocking of open() that could cause errors inside coverage.py. An example of a failure is in issue 2083_.

  • Fix: in unusual cases where a test suite intentionally exhausts the system's file descriptors to test handling errors in open(), coverage.py would fail when trying to open source files, as described in issue 2091_. This is now fixed.

  • A small tweak to the HTML report: file paths now use thin spaces around slashes to make them easier to read.

.. _issue 2081: #​2081 .. _issue 2083: #​2083 .. _pull 2085: #​2085 .. _issue 2086: #​2086 .. _pull 2090: #​2090 .. _issue 2091: #​2091

.. _changes_7-11-3:

v7.11.3

Compare Source

  • Fix: the 7.11.1 changes meant that conflicts between a requested measurement core and other settings would raise an error. This was a breaking change from previous behavior, as reported in issue 2076_ and issue 2078_.

    The previous behavior has been restored: when the requested core conflicts with other settings, another core is used instead, and a warning is issued.

  • For contributors: the repo has moved from Ned's nedbat GitHub account_ to the coveragepy GitHub organization_. The default branch has changed from master to main.

.. _issue 2076: #​2076 .. _issue 2078: #​2078 .. _nedbat GitHub account: https://github.com/nedbat .. _coveragepy GitHub organization: https://github.com/coveragepy

.. _changes_7-11-2:

v7.11.2

Compare Source

  • Fix: using the "sysmon" measurement core in 7.11.1, if Python code was claimed to come from a non-Python file, a NotPython exception could be raised. This could happen for example with Jinja templates compiled to Python, as reported in issue 2077_. This is now fixed.

  • Doc: corrected the first entry in the 7.11.1 changelog.

.. _issue 2077: #​2077

.. _changes_7-11-1:

v7.11.1

Compare Source

  • Fix: some chanages to details of how the measurement core is chosen, and how conflicting settings are handled. The "sysmon" core cannot be used with some conurrency settings, with dynamic context, and in Python 3.12/3.13, with branch measurement.

    • If the core is not specified and defaults to "sysmon" (Python 3.14+), but other settings conflict with sysmon, then the "ctrace" core will be used instead with no warning. For concurrency conflicts, this used to produce an error, as described in issue 2064_.

    • If the "sysmon" core is explicitly requested in your configuration, but other settings conflict, an error is now raised. This used to produce a warning.

  • Fix: some multi-line case clauses or for loops (and probably other constructs) could cause incorrect claims of missing branches with the sys.monitoring core, as described in issue 2070_. This is now fixed.

  • Fix: when running in pytest under coverage, a breakpoint() would stop in the wrong frame, one level down from where it should, as described in issue 1420_. This was due to a coverage change in v6.4.1 that seemed to give a slight performance improvement, but I couldn't reproduce the performance gain, so it's been reverted, fixing the debugger problem.

  • A new debug option --debug=core shows which core is in use and why.

  • Split sqlite debugging information out of the sys :ref:coverage debug <cmd_debug> and :ref:cmd_run_debug options since it's bulky and not very useful.

  • Updated the :ref:howitworks page to better describe the three different measurement cores.

.. _issue 1420: #​1420 .. _issue 2064: #​2064 .. _issue 2070: #​2070

.. _changes_7-11-0:

editorconfig-checker/editorconfig-checker.python (editorconfig-checker/editorconfig-checker.python)

v3.5.0

Compare Source

v3.4.1

Compare Source

v3.4.0

Compare Source

v3.3.0

Compare Source

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

v2.43.0

Compare Source

Features
  • Add public wrapper for _mtls_helper.check_use_client_cert which enables mTLS if GOOGLE_API_USE_CLIENT_CERTIFICATE is not set, when the MWID/X.509 cert sources detected (#​1859) Add public wrapper for check_use_client_cert which enables mTLS if GOOGLE_API_USE_CLIENT_CERTIFICATE is not set, when the MWID/X.509 cert sources detected. Also, fix check_use_client_cert to return boolean value. Change #​1848 added the check_use_client_cert method that helps know if client cert should be used for mTLS connection. However, that was in a private class, thus, created a public wrapper of the same function so that it can be used by python Client Libraries. Also, updated check_use_client_cert to return a boolean value instead of existing string value for better readability and future scope. --------- (1535eccbff0ad8f3fd6a9775316ac8b77dca66ba)
  • Enable mTLS if GOOGLE_API_USE_CLIENT_CERTIFICATE is not set, if the MWID/X.509 cert sources detected (#​1848) The Python SDK will use a hybrid approach for mTLS enablement:
  • If the GOOGLE_API_USE_CLIENT_CERTIFICATE environment variable is set (either true or false), the SDK will respect that setting. This is necessary for test scenarios and users who need to explicitly control mTLS behavior.
  • If the GOOGLE_API_USE_CLIENT_CERTIFICATE environment variable is not set, the SDK will automatically enable mTLS only if it detects Managed Workload Identity (MWID) or X.509 Workforce Identity Federation (WIF) certificate sources. In other cases where the variable is not set, mTLS will remain disabled. ** This change also adds the helper method check_use_client_cert and it's unit test, which will be used for checking the criteria for setting the mTLS to true ** This change is only for Auth-Library, other changes will be created for Client-Library use-cases. --------- (395e405b64b56ddb82ee639958c2e8056ad2e82b)

v2.42.1

Compare Source

Bug Fixes

v2.42.0

Compare Source

Features
Bug Fixes

v2.41.1

Compare Source

Bug Fixes

v2.41.0

Compare Source

Features
Bug Fixes
Documentation

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)
googleapis/python-pubsub (google-cloud-pubsub)

v2.33.0

Compare Source

Features
  • Add AwsKinesisFailureReason.ApiViolationReason (ac68093)
  • Add tags to Subscription, Topic, and CreateSnapshotRequest messages for use in CreateSubscription, CreateTopic, and CreateSnapshot requests respectively (ac68093)
  • Annotate some resource fields with their corresponding API types (ac68093)
Bug Fixes
  • Deprecate credentials_file argument (ac68093)
Documentation
  • A comment for field received_messages in message .google.pubsub.v1.StreamingPullResponse is changed (ac68093)

v2.32.0

Compare Source

Features
Bug Fixes
microsoftgraph/msgraph-sdk-python (msgraph-sdk)

v1.49.0

Compare Source

Features
  • generation: update request builders and models (c596dca)

v1.48.0

Compare Source

Features

v1.47.0

Compare Source

Features
  • generation: update request builders and models (2772eb5)
  • generation: update request builders and models (6fc8672)

v1.46.0

Compare Source

Features
  • generation: update request builders and models (8ace06e)

v1.45.0

Compare Source

Features
  • generation: update request builders and models (9b00d33)

v1.44.0

Compare Source

Features
  • generation: update request builders and models (c73f3af)

v1.40.0

Compare Source

Features
  • generation: update request builders and models (15c9742)

v1.39.0

Compare Source

Features
  • generation: update request builders and models (cd04cfb)

v1.38.0

Compare Source

Features
  • generation: update request builders and models (47a564d)
  • generation: update request builders and models (b35949b)

v1.37.0

Compare Source

Features
  • generation: update request builders and models (f7de565)

v1.36.0

Compare Source

Features
  • generation: update request builders and models (7f49d36)

v1.35.0

Compare Source

Features
  • generation: update request builders and models (5a3dc37)

v1.34.0

Compare Source

Features
  • generation: update request builders and models (49dbc7e)

v1.33.0

Compare Source

Features
  • generation: update request builders and models (2cb94a6)

v1.32.0

Compare Source

Features
  • generation: update request builders and models (48cf860)

v1.31.0

Compare Source

Features
  • generation: update request builders and models (f445a90)

v1.30.0

Compare Source

Features
  • generation: update request builders and models (303fb7d)

v1.29.0

Compare Source

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

v4.5.0

Compare Source

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

Features

v4.4.0

Compare Source

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

Features
Fixes
pre-commit/mirrors-mypy (pre-commit/mirrors-mypy)

v1.18.2

Compare Source

v1.18.1

Compare Source

v1.17.1

Compare Source

v1.17.0

Compare Source

v1.16.1

Compare Source

v1.16.0

Compare Source

psf/black (psf/black)

v25.11.0

Compare Source

Highlights
  • Enable base 3.14 support (#​4804)
  • Add support for the new Python 3.14 t-string syntax introduced by PEP 750 (#​4805)
Stable style
  • Fix bug where comments between # fmt: off and # fmt: on were reformatted (#​4811)
  • Comments containing fmt directives now preserve their exact formatting instead of being normalized (#​4811)
Preview style
  • Move multiline_string_handling from --unstable to --preview (#​4760)
  • Fix bug where module docstrings would be treated as normal strings if preceded by comments (#​4764)
  • Fix bug where python 3.12 generics syntax split line happens weirdly (#​4777)
  • Standardize type comments to form # type: <value> (#​4645)
  • Fix fix_fmt_skip_in_one_liners preview feature to respect # fmt: skip for compound statements with semicolon-separated bodies (#​4800)
Configuration
  • Add no_cache option to control caching behavior. (#​4803)
Packaging
  • Releases now include arm64 Linux binaries (#​4773)
  • Releases now include arm64 Windows binaries and wheels (#​4814)
Output
  • Write unchanged content to stdout when excluding formatting from stdin using pipes (#​4610)
Blackd
  • Implemented BlackDClient. This simple python client allows to easily send formatting requests to blackd (#​4774)
Integrations
  • Enable 3.14 base CI (#​4804)
  • Enhance GitHub Action psf/black to support the required-version major-version-only "stability" format when using pyproject.toml (#​4770)
  • Improve error message for vim plugin users. It now handles independently vim version
  • Vim: Warn on unsupported Vim and Python versions independently (#​4772)
  • Vim: Print the import paths when importing black fails (#​4675)
  • Vim: Fix handling of virtualenvs that have a different Python version (#​4675)
pydantic/pydantic (pydantic)

v2.12.4: 2025-11-05

Compare Source

v2.12.4 (2025-11-05)

This is the fourth 2.12 patch release, fixing more regressions, and reverting a change in the build() method of the AnyUrl and Dsn types.

This patch release also fixes an issue with the serialization of IP address types, when serialize_as_any is used. The next patch release will try to address the remaining issues with serialize as any behavior by introducing a new polymorphic serialization feature, that should be used in most cases in place of serialize as any.

Full Changelog: https://github.com/pydantic/pydantic/compare/v2.12.3...v2.12.4

v2.12.3

Compare Source

GitHub release

What's Changed

This is the third 2.12 patch release, fixing issues related to the FieldInfo class, and reverting a change to the supported after model validator function signatures.

  • Raise a warning when an invalid after model validator function signature is raised by @​Viicos in #​12414. Starting in 2.12.0, using class methods for after model validators raised an error, but the error wasn't raised concistently. We decided to emit a deprecation warning instead.
  • Add FieldInfo.asdict() method, improve documentation around FieldInfo by @​Viicos in #​12411. This also add back support for mutations on FieldInfo classes, that are reused as Annotated metadata. However, note that this is still not a supported pattern. Instead, please refer to the added example in the documentation.

The blog post section on changes was also updated to document the changes related to serialize_as_any.

v2.12.2

Compare Source

GitHub release

What's Changed
Fixes
  • Release a new pydantic-core version, as a corrupted CPython 3.10 manylinux2014_aarch64 wheel got uploaded (pydantic-core#1843).
  • Fix issue with recursive generic models with a parent model class by @​Viicos in #​12398

v2.12.1

Compare Source

GitHub release

What's Changed

This is the first 2.12 patch release, addressing most (but not all yet) regressions from the initial 2.12.0 release.

Fixes
New Contributors

v2.12.0

Compare Source

GitHub release

What's Changed

This is the final 2.12 release. It features the work of 20 external contributors and provides useful new features, along with initial Python 3.14 support. Several minor changes (considered non-breaking changes according to our versioning policy) are also included in this release. Make sure to look into them before upgrading.

Note that Pydantic V1 is not compatible with Python 3.14 and greater.

Changes (see the alpha and beta releases for additional changes since 2.11):

Packaging
New Features
Fixes
New Contributors

v2.11.10

Compare Source

GitHub release

What's Changed
Fixes

v2.11.9: 2025-09-13

Compare Source

What's Changed
Fixes

Full Changelog: https://github.com/pydantic/pydantic/compare/v2.11.8...v2.11.9

v2.11.8: 2025-09-13

Compare Source

v2.11.8 (2025-09-13)

What's Changed
Fixes

Full Changelog: https://github.com/pydantic/pydantic/compare/v2.11.7...v2.11.8

pydantic/pydantic-settings (pydantic-settings)

v2.12.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/pydantic/pydantic-settings/compare/v2.11.0...v2.12.0

v2.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/pydantic/pydantic-settings/compare/2.10.1...v2.11.0

v2.10.1

Compare Source

What's Changed

Full Changelog: https://github.com/pydantic/pydantic-settings/compare/2.10.0...2.10.1

v2.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/pydantic/pydantic-settings/compare/v2.9.1...2.10.0

pytest-dev/pytest (pytest)

v8.4.2

Compare Source

pytest 8.4.2 (2025-09-03)

Bug fixes

  • #​13478: Fixed a crash when using console_output_style{.interpreted-text role="confval"} with times and a module is skipped.

  • #​13530: Fixed a crash when using pytest.approx{.interpreted-text role="func"} and decimal.Decimal{.interpreted-text role="class"} instances with the decimal.FloatOperation{.interpreted-text role="class"} trap set.

  • #​13549: No longer evaluate type annotations in Python 3.14 when inspecting function signatures.

    This prevents crashes during module collection when modules do not explicitly use from __future__ import annotations and import types for annotations within a if TYPE_CHECKING: block.

  • #​13559: Added missing [int]{.title-ref} and [float]{.title-ref} variants to the [Literal]{.title-ref} type annotation of the [type]{.title-ref} parameter in pytest.Parser.addini{.interpreted-text role="meth"}.

  • #​13563: pytest.approx{.interpreted-text role="func"} now only imports numpy if NumPy is already in sys.modules. This fixes unconditional import behavior introduced in [8.4.0]{.title-ref}.

Improved documentation

  • #​13577: Clarify that pytest_generate_tests is discovered in test modules/classes; other hooks must be in conftest.py or plugins.

Contributor-facing changes

  • #​13480: Self-testing: fixed a few test failures when run with -Wdefault or a similar override.
  • #​13547: Self-testing: corrected expected message for test_doctest_unexpected_exception in Python 3.14.
  • #​13684: Make pytest's own testsuite insensitive to the presence of the CI environment variable -- by ogrisel{.interpreted-text role="user"}.

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-env (pytest-env)

v1.2.0

Compare Source

What's Changed

Full Changelog: https://github.com/pytest-dev/pytest-env/compare/1.1.5...1.2.0

uis/devops/lib/ucam-faas-python (ucam-faas)

v0.17.5

Compare Source

Bug Fixes
  • deps: update dependency pre-commit to v4 (40e3145)

v0.17.4

Compare Source

Bug Fixes

v0.17.3

Compare Source

Bug Fixes

v0.17.2

Compare Source

Bug Fixes
  • update dependencies and pin python image (ef978b5)

v0.17.1

Compare Source

Bug Fixes
  • update repo link for PyPi (4f85ada)

v0.17.0

Compare Source

Features
  • add CloudEvent validation for webhook handler proxy (f0c880e)

v0.16.0

Compare Source

Features
  • docs: add auto-built API documentation (b3998b0)

v0.15.0

Compare Source

Features
  • support undoing functions_framework global state changes (516966e)

v0.14.1

Compare Source

v0.14.0

Compare Source

Features
  • add support for reading message payload from bucket (37f8b6e)

v0.13.0

Compare Source

Features
  • add authentication to webhook endpoint (34496a6)
Bug Fixes
  • exclude run handler function from coverage (316b70d)
  • remove JSON checking from data publishing (e81418f)

v0.12.0

Compare Source

Features
  • refactor entra webhook container (319cf45)
Bug Fixes
  • move entra webhook code into separate module (219026f)

v0.11.0

Compare Source

Features
  • add long-running task support (f11c827)
Bug Fixes
  • remove unneeded initialize argument (8f23b43)

v0.10.0

Compare Source

Features
  • push docker images to public registry (b5b68ff)

v0.9.3

Compare Source

v0.9.2

Compare Source

Bug Fixes
  • bump ci template to v6.10.0 to avoid release-it releasing twice (937dbe6)
  • remove duplicated file release-it.json (ed53ae2)

v0.9.1

Compare Source

v0.9.0

Compare Source

Features
  • add release-it config (23f78f3)
  • include traceback on unhandled exceptions (5161cef)
  • type-annotate ucam_fass and example modules (470334e)
Bug Fixes
  • correct test running locally (caa4bd9)
  • rename release-it.json to .release-it.json (b7a9c07)
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.

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

Loading