FAQ | This is a LIVE service | Changelog

Skip to content

fix(deps): update all non-major dependencies

This MR contains the following updates:

Package Change Age Confidence Type Update
cachecontrol 0.14.3 -> 0.14.4 age confidence dependencies patch
coverage 7.11.0 -> 7.12.0 age confidence dev minor
django (changelog) 4.2.25 -> 4.2.27 age confidence dependencies patch
editorconfig-checker/editorconfig-checker.python 3.4.0 -> 3.6.0 age confidence repository minor
geddit 2.1.0 -> 2.1.1 age confidence dependencies patch
google-auth 2.41.1 -> 2.43.0 age confidence dependencies minor
pre-commit 4.3.0 -> 4.5.0 age confidence dev minor
pre-commit/mirrors-mypy v1.18.2 -> v1.19.0 age confidence repository minor
ucam-identitylib 3.4.0 -> 3.4.1 age confidence dependencies patch
uis/devops/continuous-delivery/ci-templates v7.19.2 -> v7.23.1 age confidence repository minor

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

psf/cachecontrol (cachecontrol)

v0.14.4

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/psf/cachecontrol/compare/v0.14.3...v0.14.4

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:

django/django (django)

v4.2.27

Compare Source

v4.2.26

Compare Source

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

v3.6.0

Compare Source

v3.5.0

Compare Source

v3.4.1

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
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.19.0

Compare Source

uis/devops/iam/identity-lib (ucam-identitylib)

v3.4.1

Changed
  • Updated Photo API, Card API, HR and Student APIs specs.
uis/devops/continuous-delivery/ci-templates (uis/devops/continuous-delivery/ci-templates)

v7.23.1: 7.23.1

Compare Source

7.23.1 (2025-12-05)

v7.23.0: 7.23.0

Compare Source

7.23.0 (2025-11-28)
Features
  • tox-tests to use dind config from fragments (c765400)

v7.22.1: 7.22.1

Compare Source

7.22.1 (2025-11-25)
Bug Fixes
  • add missing before_script reference to dind in .terraform-test-cleanup (2852ccd)

v7.22.0: 7.22.0

Compare Source

7.22.0 (2025-11-24)
Features
  • docker-in-docker: add waiting before_script to fragment (2b0924e), closes #​178

v7.21.0: 7.21.0

Compare Source

7.21.0 (2025-11-19)

Features
  • re-work maven jobs rules (da9962b)
  • re-work maven jobs rules: try to re-name the job (4efa101)

v7.20.3: 7.20.3

Compare Source

7.20.3 (2025-11-03)
Bug Fixes
  • use only needed bits of Terraform-Module.gitlab-ci.yml to avoid duplicate jobs (ff646a0)

v7.20.2: 7.20.2

Compare Source

7.20.2 (2025-10-30)
Bug Fixes
  • check-latest-tag-in-changelog: skip job if tag is an alpha or beta release (210ffd5)

v7.20.1: 7.20.1

Compare Source

7.20.1 (2025-10-29)
Bug Fixes
  • allow no test coverage in maven (40db7bf)

v7.20.0: 7.20.0

Compare Source

7.20.0 (2025-10-28)
Features
  • add code coverage to maven jobs (53c1345)

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