fix(deps): update all non-major dependencies (!49) · Merge requests · Information Services / DevOps / Django Libraries / API Gateway Auth

This MR contains the following updates:

Package	Change	Type	Update
coverage	`7.11.0` → `7.13.1`	dev	minor
editorconfig-checker/editorconfig-checker.python	`3.4.0` → `3.6.0`	repository	minor
pre-commit	`4.3.0` → `4.5.1`	dev	minor
pre-commit/mirrors-mypy	`v1.18.2` → `v1.19.1`	repository	minor
uis/devops/continuous-delivery/ci-templates	`v7.19.2` → `v7.25.7`	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

coveragepy/coveragepy (coverage)

`v7.13.1`

Compare Source

Added: the JSON report now includes a "start_line" key for function and class regions, indicating the first line of the region in the source. Closes issue 2110_.
Added: The debug data command now takes file names as arguments on the command line, so you can inspect specific data files without needing to set the COVERAGE_FILE environment variable.
Fix: the JSON report used to report module docstrings as executed lines, which no other report did, as described in issue 2105_. This is now fixed, thanks to Jianrong Zhao.
Fix: coverage.py uses a more disciplined approach to detecting where third-party code is installed, and avoids measuring it. This shouldn't change any behavior. If you find that it does, please get in touch.
Performance: data files that will be combined now record their hash as part of the file name. This lets us skip duplicate data more quickly, speeding the combining step.
Docs: added a section explaining more about what is considered a missing branch and how it is reported: :ref:branch_explain, as requested in issue 1597. Thanks to Ayisha Mohammed <pull 2092_>.
Tests: the test suite misunderstood what core was being tested if COVERAGE_CORE wasn't set on 3.14+. This is now fixed, closing issue 2109_.

.. _issue 1597: #1597 .. _pull 2092: #2092 .. _issue 2105: #2105 .. _issue 2109: #2109 .. _issue 2110: #2110

.. _changes_7-13-0:

`v7.13.0`

Compare Source

Feature: coverage.py now supports :file:.coveragerc.toml configuration files. These files use TOML syntax and take priority over :file:pyproject.toml but lower priority than :file:.coveragerc files. Closes issue 1643_ thanks to Olena Yefymenko <pull 1952_>_.
Fix: we now include a permanent .pth file which is installed with the code, fixing issue 2084. In 7.12.1b1 this was done incorrectly: it didn't work when using the source wheel (py3-none-any). This is now fixed. Thanks, Henry Schreiner <pull 2100_>.
Deprecated: when coverage.py is installed, it creates three command entry points: coverage, coverage3, and coverage-3.10 (if installed for Python 3.10). The second and third of these are not needed and will eventually be removed. They still work for now, but print a message about their deprecation.

.. _issue 1643: #1643 .. _pull 1952: #1952 .. _pull 2100: #2100

.. _changes_7-12-1b1:

`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)

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

`v4.5.1`

Compare Source

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

Fixes

Fix language: python with repo: local without additional_dependencies.
- #3597 MR by @asottile.

`v4.5.0`

Compare Source

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

Features

Add pre-commit hazmat.
- #3585 MR by @asottile.

`v4.4.0`

Compare Source

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

Features

Add --fail-fast option to pre-commit run.
- #3528 MR by @JulianMaurin.
Upgrade ruby-build / rbenv.
- #3566 MR by @asottile.
- #3565 issue by @MRigal.
Add language: unsupported / language: unsupported_script as aliases for language: system / language: script (which will eventually be deprecated).
- #3577 MR by @asottile.
Add support docker-in-docker detection for cgroups v2.
- #3535 MR by @br-rhrbacek.
- #3360 issue by @JasonAlt.

Fixes

Handle when docker gives SecurityOptions: null.
- #3537 MR by @asottile.
- #3514 issue by @jenstroeger.
Fix error context for invalid stages in .pre-commit-config.yaml.
- #3576 MR by @asottile.