This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [coverage](https://redirect.github.com/coveragepy/coveragepy) | `==7.5.1` → `==7.14.1` |  |  | --- ### Release Notes <details> <summary>coveragepy/coveragepy (coverage)</summary> ### [`v7.14.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7141--2026-05-26) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.14.0...7.14.1) - Fix: the HTML report used typographic niceties to make file paths more readable by adding a small amount of space around slashes. Those spaces interfered with searching the page for file paths of interest. Now the report uses CSS to accomplish the same visual tweak so that searches with slashes work correctly. Closes `issue 2170`\_. - `Add a 3.16 PyPI classifier <hugo-316_>`\_ since we test on the 3.16 main branch. .. \_issue 2170: [#&#8203;2170](https://redirect.github.com/coveragepy/coveragepy/issues/2170) .. \_hugo-316: <https://mastodon.social/@&#8203;hugovk/116588523571204490> .. \_changes\_7-14-0: ### [`v7.14.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7140--2026-05-10) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.13.5...7.14.0) - Feature: now when running one of the reporting commands, if there are parallel data files that need combining, they will be implicitly combined before creating the report. There is no option to avoid the combination; let us know if you have a use case that requires it. Thanks, `Tim Hatch <pull 2162_>`*. Closes `issue 1781`*. - Fix: the output from `combine` was too verbose, listing each file considered. Now it shows a single line with the counts of files combined, files skipped, and files with errors. The `-q` flag suppresses this line. The old detailed lines are available with the new `--debug=combine` option. - Fix: running a Python file through a symlink now sets the sys.path correctly, matching regular Python behavior. Fixes `issue 2157`\_. - Fix: `Collector.flush_data` could fail with "RuntimeError: Set changed size during iteration" when a tracer in another thread added a line to the per-file set that `add_lines` (or `add_arcs`) was iterating. The values passed to `CoverageData` are now snapshotted via `dict.copy()` and `set.copy()`, which are atomic under the GIL. Thanks, `Alex Vandiver <pull 2165_>`\_. - Fix: the soft keyword `lazy` is now bolded in HTML reports. - We are no longer testing eventlet support. Eventlet started issuing stern deprecation warnings that break our tests. Our support code is still there. .. \_issue 1781: [#&#8203;1781](https://redirect.github.com/coveragepy/coveragepy/issues/1781) .. \_issue 2157: [#&#8203;2157](https://redirect.github.com/coveragepy/coveragepy/issues/2157) .. \_pull 2162: [#&#8203;2162](https://redirect.github.com/coveragepy/coveragepy/pull/2162) .. \_pull 2165: [#&#8203;2165](https://redirect.github.com/coveragepy/coveragepy/pull/2165) .. \_changes\_7-13-5: ### [`v7.13.5`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7135--2026-03-17) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.13.4...7.13.5) - Fix: `issue 2138`\_ describes a memory leak that happened when repeatedly using the Coverage API with in-memory data. This is now fixed. - Fix: the markdown-formatted coverage report didn't fully escape special characters in file paths (`issue 2141`*). This would be very unlikely to cause a problem, but now it's done properly, thanks to `Ellie Ayla <pull 2142_>`*. - Fix: the C extension wouldn't build on VS2019, but now it does (`issue 2145`\_). .. \_issue 2138: [#&#8203;2138](https://redirect.github.com/coveragepy/coveragepy/issues/2138) .. \_issue 2141: [#&#8203;2141](https://redirect.github.com/coveragepy/coveragepy/issues/2141) .. \_pull 2142: [#&#8203;2142](https://redirect.github.com/coveragepy/coveragepy/pull/2142) .. \_issue 2145: [#&#8203;2145](https://redirect.github.com/coveragepy/coveragepy/issues/2145) .. \_changes\_7-13-4: ### [`v7.13.4`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7134--2026-02-09) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.13.3...7.13.4) - Fix: the third-party code fix in 7.13.3 required examining the parent directories where coverage was run. In the unusual situation that one of the parent directories is unreadable, a PermissionError would occur, as described in `issue 2129`\_. This is now fixed. - Fix: in test suites that change sys.path, coverage.py could fail with "RuntimeError: Set changed size during iteration" as described and fixed in `pull 2130`\_. Thanks, Noah Fatsi. - We now publish ppc64le wheels, thanks to `Pankhudi Jain <pull 2121_>`\_. .. \_pull 2121: [#&#8203;2121](https://redirect.github.com/coveragepy/coveragepy/pull/2121) .. \_issue 2129: [#&#8203;2129](https://redirect.github.com/coveragepy/coveragepy/issues/2129) .. \_pull 2130: [#&#8203;2130](https://redirect.github.com/coveragepy/coveragepy/pull/2130) .. \_changes\_7-13-3: ### [`v7.13.3`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7133--2026-02-03) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.13.2...7.13.3) - Fix: in some situations, third-party code was measured when it shouldn't have been, slowing down test execution. This happened with layered virtual environments such as uv sometimes makes. The problem is fixed, closing `issue 2082`\_. Now any directory on sys.path that is inside a virtualenv is considered third-party code. .. \_issue 2082: [#&#8203;2082](https://redirect.github.com/coveragepy/coveragepy/issues/2082) .. \_changes\_7-13-2: ### [`v7.13.2`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7132--2026-01-25) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.13.1...7.13.2) - Fix: when Python is installed via symlinks, for example with Homebrew, the standard library files could be incorrectly included in coverage reports. This is now fixed, closing `issue 2115`\_. - Fix: if a data file is created with no read permissions, the combine step would fail completely. Now a warning is issued and the file is skipped. Closes `issue 2117`\_. .. \_issue 2115: [#&#8203;2115](https://redirect.github.com/coveragepy/coveragepy/issues/2115) .. \_issue 2117: [#&#8203;2117](https://redirect.github.com/coveragepy/coveragepy/issues/2117) .. \_changes\_7-13-1: ### [`v7.13.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7131--2025-12-28) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.13.0...7.13.1) - 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: [#&#8203;1597](https://redirect.github.com/coveragepy/coveragepy/issues/1597) .. \_pull 2092: [#&#8203;2092](https://redirect.github.com/coveragepy/coveragepy/pull/2092) .. \_issue 2105: [#&#8203;2105](https://redirect.github.com/coveragepy/coveragepy/issues/2105) .. \_issue 2109: [#&#8203;2109](https://redirect.github.com/coveragepy/coveragepy/issues/2109) .. \_issue 2110: [#&#8203;2110](https://redirect.github.com/coveragepy/coveragepy/issues/2110) .. \_changes\_7-13-0: ### [`v7.13.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7130--2025-12-08) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.12.0...7.13.0) - 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: [#&#8203;1643](https://redirect.github.com/coveragepy/coveragepy/issues/1643) .. \_pull 1952: [#&#8203;1952](https://redirect.github.com/coveragepy/coveragepy/pull/1952) .. \_pull 2100: [#&#8203;2100](https://redirect.github.com/coveragepy/coveragepy/pull/2100) .. \_changes\_7-12-1b1: ### [`v7.12.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7120--2025-11-18) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.11.3...7.12.0) - 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: [#&#8203;2081](https://redirect.github.com/coveragepy/coveragepy/issues/2081) .. \_issue 2083: [#&#8203;2083](https://redirect.github.com/coveragepy/coveragepy/issues/2083) .. \_pull 2085: [#&#8203;2085](https://redirect.github.com/coveragepy/coveragepy/pull/2085) .. \_issue 2086: [#&#8203;2086](https://redirect.github.com/coveragepy/coveragepy/issues/2086) .. \_pull 2090: [#&#8203;2090](https://redirect.github.com/coveragepy/coveragepy/pull/2090) .. \_issue 2091: [#&#8203;2091](https://redirect.github.com/coveragepy/coveragepy/issues/2091) .. \_changes\_7-11-3: ### [`v7.11.3`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7113--2025-11-09) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.11.2...7.11.3) - 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: [#&#8203;2076](https://redirect.github.com/coveragepy/coveragepy/issues/2076) .. \_issue 2078: [#&#8203;2078](https://redirect.github.com/coveragepy/coveragepy/issues/2078) .. \_nedbat GitHub account: <https://github.com/nedbat> .. \_coveragepy GitHub organization: <https://github.com/coveragepy> .. \_changes\_7-11-2: ### [`v7.11.2`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7112--2025-11-08) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.11.1...7.11.2) - 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: [#&#8203;2077](https://redirect.github.com/coveragepy/coveragepy/issues/2077) .. \_changes\_7-11-1: ### [`v7.11.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7111--2025-11-07) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.11.0...7.11.1) - 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: [#&#8203;1420](https://redirect.github.com/coveragepy/coveragepy/issues/1420) .. \_issue 2064: [#&#8203;2064](https://redirect.github.com/coveragepy/coveragepy/issues/2064) .. \_issue 2070: [#&#8203;2070](https://redirect.github.com/coveragepy/coveragepy/issues/2070) .. \_changes\_7-11-0: ### [`v7.11.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7110--2025-10-15) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.7...7.11.0) - Dropped support for Python 3.9, declared support for Python 3.15 alpha. .. \_changes\_7-10-7: ### [`v7.10.7`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7107--2025-09-21) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.6...7.10.7) - Performance: with branch coverage in large files, generating HTML, JSON, or LCOV reports could take far too long due to some quadratic behavior when creating the function and class index pages. This is now fixed, closing `issue 2048`\_. Thanks to Daniel Diniz for help diagnosing the problem. - Most warnings and a few errors now have links to a page in the docs explaining the specific message. Closes `issue 1921`\_. .. \_issue 1921: [#&#8203;1921](https://redirect.github.com/coveragepy/coveragepy/issues/1921) .. \_issue 2048: [#&#8203;2048](https://redirect.github.com/coveragepy/coveragepy/issues/2048) .. \_changes\_7-10-6: ### [`v7.10.6`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7106--2025-08-29) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.5...7.10.6) - Fix: `source` directories were not properly communicated to subprocesses that ran in different directories, as reported in `issue 1499`\_. This is now fixed. - Performance: `Alex Gaynor continues fine-tuning <pull 2038_>`\_ the speed of combination, especially with many contexts. .. \_issue 1499: [#&#8203;1499](https://redirect.github.com/coveragepy/coveragepy/issues/1499) .. \_pull 2038: [#&#8203;2038](https://redirect.github.com/coveragepy/coveragepy/pull/2038) .. \_changes\_7-10-5: ### [`v7.10.5`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7105--2025-08-23) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.4...7.10.5) - Big speed improvements for `coverage combine`: it's now about twice as fast! Huge thanks to Alex Gaynor for pull requests `2032 <pull 2032_>`*, `2033 <pull 2033_>`*, and `2034 <pull 2034_>`\_. .. \_pull 2032: [#&#8203;2032](https://redirect.github.com/coveragepy/coveragepy/pull/2032) .. \_pull 2033: [#&#8203;2033](https://redirect.github.com/coveragepy/coveragepy/pull/2033) .. \_pull 2034: [#&#8203;2034](https://redirect.github.com/coveragepy/coveragepy/pull/2034) .. \_changes\_7-10-4: ### [`v7.10.4`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7104--2025-08-16) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.3...7.10.4) - Added `patch = fork` for times when the built-in forking support is insufficient. - Fix: `patch = execv` also inherits the entire coverage configuration now. .. \_changes\_7-10-3: ### [`v7.10.3`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7103--2025-08-10) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.2...7.10.3) - Fixes for `patch = subprocess`: - If subprocesses spawned yet more subprocesses simultaneously, some coverage could be missed. This is now fixed, closing `issue 2024`\_. - If subprocesses were created in other directories, their data files were stranded there and not combined into the totals, as described in `issue 2025`\_. This is now fixed. - On Windows (or maybe only some Windows?) the patch would fail with a `ModuleNotFound` error trying to import coverage. This is now fixed, closing `issue 2022`\_. - Originally only options set in the coverage configuration file would apply to subprocesses. Options set on the `coverage run` command line (such as `--branch`) wouldn't be communicated to the subprocesses. This could lead to combining failures, as described in `issue 2021`\_. Now the entire configuration is used in subprocesses, regardless of its origin. - Added `debug=patch` to help diagnose problems. - Fix: really close all SQLite databases, even in-memory ones. Closes `issue 2017`\_. .. \_issue 2017: [#&#8203;2017](https://redirect.github.com/coveragepy/coveragepy/issues/2017) .. \_issue 2021: [#&#8203;2021](https://redirect.github.com/coveragepy/coveragepy/issues/2021) .. \_issue 2022: [#&#8203;2022](https://redirect.github.com/coveragepy/coveragepy/issues/2022) .. \_issue 2024: [#&#8203;2024](https://redirect.github.com/coveragepy/coveragepy/issues/2024) .. \_issue 2025: [#&#8203;2025](https://redirect.github.com/coveragepy/coveragepy/issues/2025) .. \_changes\_7-10-2: ### [`v7.10.2`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7102--2025-08-03) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.1...7.10.2) - Fix: some code with NOP bytecodes could report missing branches that are actually executed. This is now fixed, closing `issue 1999`\_. Python 3.9 still shows the problem. .. \_issue 1999: [#&#8203;1999](https://redirect.github.com/coveragepy/coveragepy/issues/1999) .. \_changes\_7-10-1: ### [`v7.10.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7101--2025-07-27) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.10.0...7.10.1) - Fix: the exclusion for `if TYPE_CHECKING:` was wrong: it marked the branch as partial, but it should have been a line exclusion so the entire clause would be excluded. Improves `issue 831`\_. - Fix: changed where .pth files are written for `patch = subprocess`, closing `issue 2006`\_. .. \_issue 2006: [#&#8203;2006](https://redirect.github.com/coveragepy/coveragepy/issues/2006) .. \_changes\_7-10-0: ### [`v7.10.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7100--2025-07-24) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.9.2...7.10.0) - A new configuration option: ":ref:`config_run_patch`" specifies named patches to work around some limitations in coverage measurement. These patches are available: - `patch = _exit` lets coverage save its data even when :func:`os._exit() <python:os._exit>` is used to abruptly end the process. This closes long-standing `issue 310`\_ as well as its duplicates: `issue 312`*, `issue 1673`*, `issue 1845`*, and `issue 1941`*. - `patch = subprocess` measures coverage in Python subprocesses created with :mod:`subprocess`, :func:`os.system`, or one of the :func:`execv <python:os.execl>` or :func:`spawnv <python:os.spawnl>` family of functions. Closes old `issue 367`*, its duplicate `issue 378`* and old `issue 689`\_. - `patch = execv` adjusts the :func:`execv <python:os.execl>` family of functions to save coverage data before ending the current program and starting the next. Not available on Windows. Closes `issue 43`\_ after 15 years! - The HTML report now dimly colors subsequent lines in multi-line statements. They used to have no color. This gives a better indication of the amount of code missing in the report. Closes `issue 1308`\_. - Two new exclusion patterns are part of the defaults: `...` is automatically excluded as a line and `if TYPE_CHECKING:` is excluded as a branch. Closes `issue 831`\_. - A new command-line option: `--save-signal=USR1` specifies a signal that coverage.py will listen for. When the signal is sent, the coverage data will be saved. This makes it possible to save data from within long-running processes. Thanks, `Arkady Gilinsky <pull 1998_>`\_. - A new configuration option: ":ref:`config_report_partial_also`" is a list of regexes to add as pragmas for partial branches. This parallels the ":ref:`config_report_exclude_also`" setting for adding line exclusion patterns. - A few file path configuration settings didn't allow for tilde expansion: :ref:`config_json_output`, :ref:`config_lcov_output` and :ref:`config_run_debug_file`. This is now fixed. - Wheels are included for 3.14 now that 3.14 rc1 is available. - We no longer ship a PyPy-specific wheel. PyPy will install the pure-Python wheel. Closes `issue 2001`\_. - In the very unusual situation of not having a current frame, coverage no longer crashes when using the sysmon core, fixing `issue 2005`\_. .. \_issue 43: [#&#8203;43](https://redirect.github.com/coveragepy/coveragepy/issues/43) .. \_issue 310: [#&#8203;310](https://redirect.github.com/coveragepy/coveragepy/issues/310) .. \_issue 312: [#&#8203;312](https://redirect.github.com/coveragepy/coveragepy/issues/312) .. \_issue 367: [#&#8203;367](https://redirect.github.com/coveragepy/coveragepy/issues/367) .. \_issue 378: [#&#8203;378](https://redirect.github.com/coveragepy/coveragepy/issues/378) .. \_issue 689: [#&#8203;689](https://redirect.github.com/coveragepy/coveragepy/issues/689) .. \_issue 831: [#&#8203;831](https://redirect.github.com/coveragepy/coveragepy/issues/831) .. \_issue 1308: [#&#8203;1308](https://redirect.github.com/coveragepy/coveragepy/issues/1308) .. \_issue 1673: [#&#8203;1673](https://redirect.github.com/coveragepy/coveragepy/issues/1673) .. \_issue 1845: [#&#8203;1845](https://redirect.github.com/coveragepy/coveragepy/issues/1845) .. \_issue 1941: [#&#8203;1941](https://redirect.github.com/coveragepy/coveragepy/issues/1941) .. \_pull 1998: [#&#8203;1998](https://redirect.github.com/coveragepy/coveragepy/pull/1998) .. \_issue 2001: [#&#8203;2001](https://redirect.github.com/coveragepy/coveragepy/issues/2001) .. \_issue 2005: [#&#8203;2005](https://redirect.github.com/coveragepy/coveragepy/issues/2005) .. \_changes\_7-9-2: ### [`v7.9.2`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-792--2025-07-03) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.9.1...7.9.2) - Fix: complex conditionals within a line might cause a KeyError when using sys.monitoring, as reported in `issue 1991`\_. This is now fixed. - Fix: we can now measure coverage for code in Python archive (.par) files. Thanks, `Itamer Oren <pull 1984_>`\_. .. \_pull 1984: [#&#8203;1984](https://redirect.github.com/coveragepy/coveragepy/pull/1984) .. \_issue 1991: [#&#8203;1991](https://redirect.github.com/coveragepy/coveragepy/issues/1991) .. \_changes\_7-9-1: ### [`v7.9.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-791--2025-06-13) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.9.0...7.9.1) - 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`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-790--2025-06-11) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.8.2...7.9.0) - 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: [#&#8203;1746](https://redirect.github.com/coveragepy/coveragepy/issues/1746) .. \_issue 1977: [#&#8203;1977](https://redirect.github.com/coveragepy/coveragepy/issues/1977) .. \_pull 1978: [#&#8203;1978](https://redirect.github.com/coveragepy/coveragepy/pull/1978) .. \_issue 1980: [#&#8203;1980](https://redirect.github.com/coveragepy/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`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-782--2025-05-23) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.8.1...7.8.2) - Wheels are provided for Windows ARM64 on Python 3.11, 3.12, and 3.13. Thanks, `Finn Womack <pull 1972_>`\_. .. \_issue 1971: [#&#8203;1971](https://redirect.github.com/coveragepy/coveragepy/pull/1971) .. \_pull 1972: [#&#8203;1972](https://redirect.github.com/coveragepy/coveragepy/pull/1972) .. \_changes\_7-8-1: ### [`v7.8.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-781--2025-05-21) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.8.0...7.8.1) - 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: [#&#8203;1966](https://redirect.github.com/coveragepy/coveragepy/issues/1966) .. \_pull 1967: [#&#8203;1967](https://redirect.github.com/coveragepy/coveragepy/pull/1967) .. \_issue 1970: [#&#8203;1970](https://redirect.github.com/coveragepy/coveragepy/issues/1970) .. \_changes\_7-8-0: ### [`v7.8.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-780--2025-03-30) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.7.1...7.8.0) - 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: [#&#8203;1696](https://redirect.github.com/coveragepy/coveragepy/issues/1696) .. \_pull 1700: [#&#8203;1700](https://redirect.github.com/coveragepy/coveragepy/pull/1700) .. \_issue 1942: [#&#8203;1942](https://redirect.github.com/coveragepy/coveragepy/issues/1942) .. \_pull 1943: [#&#8203;1943](https://redirect.github.com/coveragepy/coveragepy/pull/1943) .. \_changes\_7-7-1: ### [`v7.7.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-771--2025-03-21) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.7.0...7.7.1) - A few small tweaks to the sys.monitoring support for Python 3.14. Please test! .. \_changes\_7-7-0: ### [`v7.7.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-770--2025-03-16) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.12...7.7.0) - 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: [#&#8203;1888](https://redirect.github.com/coveragepy/coveragepy/issues/1888) .. \_pull 1919: [#&#8203;1919](https://redirect.github.com/coveragepy/coveragepy/pull/1919) .. \_changes\_7-6-12: ### [`v7.6.12`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7612--2025-02-11) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.11...7.6.12) - Fix: some aarch64 distributions were missing (`issue 1927`\_). These are now building reliably. .. \_issue 1927: [#&#8203;1927](https://redirect.github.com/coveragepy/coveragepy/issues/1927) .. \_changes\_7-6-11: ### [`v7.6.11`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7611--2025-02-08) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.10...7.6.11) - Fix: a memory leak in CTracer has been fixed. The details are in `issue 1924`\_ and `pytest-dev 676`\_. This should reduce the memory footprint for everyone even if it hadn't caused a problem before. - We now ship a py3-none-any.whl wheel file. Thanks, `Russell Keith-Magee <pull 1914_>`\_. .. \_pull 1914: [#&#8203;1914](https://redirect.github.com/coveragepy/coveragepy/pull/1914) .. \_issue 1924: [#&#8203;1924](https://redirect.github.com/coveragepy/coveragepy/issues/1924) .. \_pytest-dev 676: [pytest-dev/pytest-cov#676](https://redirect.github.com/pytest-dev/pytest-cov/issues/676) .. \_changes\_7-6-10: ### [`v7.6.10`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7610--2024-12-26) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.9...7.6.10) - Fix: some descriptions of missing branches in HTML and LCOV reports were incorrect when multi-line statements were involved (`issue 1874`\_ and `issue 1875`\_). These are now fixed. - Fix: Python 3.14 `defers evaluation of annotations <pep649_>`\_ by moving them into separate code objects. That code is rarely executed, so coverage.py would mark them as missing, as reported in `issue 1908`\_. Now they are ignored by coverage automatically. - Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving mocks, imports, and trace functions: `issue 1902`\_. To be honest, I don't understand the problem or the solution, but `git bisect` helped find it, and now it's fixed. - Docs: re-wrote the :ref:`subprocess` page to put multiprocessing first and to highlight the correct use of :class:`multiprocessing.Pool <python:multiprocessing.pool.Pool>`. .. \_issue 1874: [#&#8203;1874](https://redirect.github.com/coveragepy/coveragepy/issues/1874) .. \_issue 1875: [#&#8203;1875](https://redirect.github.com/coveragepy/coveragepy/issues/1875) .. \_issue 1902: [#&#8203;1902](https://redirect.github.com/coveragepy/coveragepy/issues/1902) .. \_issue 1908: [#&#8203;1908](https://redirect.github.com/coveragepy/coveragepy/issues/1908) .. \_pep649: <https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-deferred-annotations> .. \_changes\_7-6-9: ### [`v7.6.9`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-769--2024-12-06) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.8...7.6.9) - Fix: `Tomas Uribe fixed <pull 1901_>`\_ a performance problem in the XML report. Large code bases should produce XML reports much faster now. .. \_pull 1901: [#&#8203;1901](https://redirect.github.com/coveragepy/coveragepy/pull/1901) .. \_changes\_7-6-8: ### [`v7.6.8`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-768--2024-11-23) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.7...7.6.8) - Fix: the LCOV report code assumed that a branch line that took no branches meant that the entire line was unexecuted. This isn't true in a few cases: the line might always raise an exception, or might have been optimized away. Fixes `issue 1896`\_. - Fix: similarly, the HTML report will now explain that a line that jumps to none of its expected destinations must have always raised an exception. Previously, it would say something nonsensical like, "line 4 didn't jump to line 5 because line 4 was never true, and it didn't jump to line 7 because line 4 was always true." This was also shown in `issue 1896`\_. .. \_issue 1896: [#&#8203;1896](https://redirect.github.com/coveragepy/coveragepy/issues/1896) .. \_changes\_7-6-7: ### [`v7.6.7`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-767--2024-11-15) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.6...7.6.7) - Fix: ugh, the other assert from 7.6.5 can also be encountered in the wild, so it's been restored to a conditional. Sorry for the churn. .. \_changes\_7-6-6: ### [`v7.6.6`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-766--2024-11-15) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.5...7.6.6) - One of the new asserts from 7.6.5 caused problems in real projects, as reported in `issue 1891`\_. The assert has been removed. .. \_issue 1891: [#&#8203;1891](https://redirect.github.com/coveragepy/coveragepy/issues/1891) .. \_changes\_7-6-5: ### [`v7.6.5`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-765--2024-11-14) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.4...7.6.5) - Fix: fine-tuned the exact Python version (3.12.6) when exiting from `with` statements changed how they traced. This affected whether people saw the fix for `issue 1880`\_. - Fix: isolate our code more from mocking in the os module that in rare cases can cause `bizarre behavior <pytest-cov-666_>`\_. - Refactor: some code unreachable code paths in parser.py were changed to asserts. If you encounter any of these, please let me know! .. \_pytest-cov-666: [pytest-dev/pytest-cov#666](https://redirect.github.com/pytest-dev/pytest-cov/issues/666) .. \_changes\_7-6-4: ### [`v7.6.4`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-764--2024-10-20) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.3...7.6.4) - Fix: multi-line `with` statements could cause contained branches to be incorrectly marked as missing (`issue 1880`\_). This is now fixed. .. \_issue 1880: [#&#8203;1880](https://redirect.github.com/coveragepy/coveragepy/issues/1880) .. \_changes\_7-6-3: ### [`v7.6.3`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-763--2024-10-13) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.2...7.6.3) - Fix: nested context managers could incorrectly be analyzed to flag a missing branch on the last context manager, as described in `issue 1876`\_. This is now fixed. - Fix: the missing branch message about not exiting a module had an extra "didn't," as described in `issue 1873`\_. This is now fixed. .. \_issue 1873: [#&#8203;1873](https://redirect.github.com/coveragepy/coveragepy/issues/1873) .. \_issue 1876: [#&#8203;1876](https://redirect.github.com/coveragepy/coveragepy/issues/1876) .. \_changes\_7-6-2: ### [`v7.6.2`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-762--2024-10-09) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.1...7.6.2) - Dropped support for Python 3.8 and PyPy 3.8. - Fix: a final wildcard match/case clause assigning to a name (`case _ as value`) was incorrectly marked as a missing branch. This is now fixed, closing `issue 1860`\_. - Fewer things are considered branches now. Lambdas, comprehensions, and generator expressions are no longer marked as missing branches if they don't complete execution. Closes `issue 1852`\_. - Fix: the HTML report didn't properly show multi-line f-strings that end with a backslash continuation. This is now fixed, closing `issue 1836`*, thanks to `LiuYinCarl and Marco Ricci <pull 1838_>`*. - Fix: the LCOV report now has correct line numbers (fixing `issue 1846`*) and better branch descriptions for BRDA records (fixing `issue 1850`*). There are other changes to lcov also, including a new configuration option :ref:`line_checksums <config_lcov_line_checksums>` to control whether line checksums are included in the lcov report. The default is false. To keep checksums set it to true. All this work is thanks to Zack Weinberg (`pull 1849`\_ and `pull 1851`\_). - Fixed the docs for multi-line regex exclusions, closing `issue 1863`\_. - Fixed a potential crash in the C tracer, closing `issue 1835`*, thanks to `Jan Kühle <pull 1843_>`*. .. \_issue 1835: [#&#8203;1835](https://redirect.github.com/coveragepy/coveragepy/issues/1835) .. \_issue 1836: [#&#8203;1836](https://redirect.github.com/coveragepy/coveragepy/issues/1836) .. \_pull 1838: [#&#8203;1838](https://redirect.github.com/coveragepy/coveragepy/pull/1838) .. \_pull 1843: [#&#8203;1843](https://redirect.github.com/coveragepy/coveragepy/pull/1843) .. \_issue 1846: [#&#8203;1846](https://redirect.github.com/coveragepy/coveragepy/issues/1846) .. \_pull 1849: [#&#8203;1849](https://redirect.github.com/coveragepy/coveragepy/pull/1849) .. \_issue 1850: [#&#8203;1850](https://redirect.github.com/coveragepy/coveragepy/issues/1850) .. \_pull 1851: [#&#8203;1851](https://redirect.github.com/coveragepy/coveragepy/pull/1851) .. \_issue 1852: [#&#8203;1852](https://redirect.github.com/coveragepy/coveragepy/issues/1852) .. \_issue 1860: [#&#8203;1860](https://redirect.github.com/coveragepy/coveragepy/issues/1860) .. \_issue 1863: [#&#8203;1863](https://redirect.github.com/coveragepy/coveragepy/issues/1863) .. \_changes\_7-6-1: ### [`v7.6.1`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7612--2025-02-11) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.6.0...7.6.1) - Fix: some aarch64 distributions were missing (`issue 1927`\_). These are now building reliably. .. \_issue 1927: [#&#8203;1927](https://redirect.github.com/coveragepy/coveragepy/issues/1927) .. \_changes\_7-6-11: ### [`v7.6.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-760--2024-07-11) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.5.4...7.6.0) - Exclusion patterns can now be multi-line, thanks to `Daniel Diniz <pull 1807_>`*. This enables many interesting exclusion use-cases, including those requested in issues `118 <issue 118_>`* (entire files), `996 <issue 996_>`\_ (multiple lines only when appearing together), `1741 <issue 1741_>`\_ (remainder of a function), and `1803 <issue 1803_>`\_ (arbitrary sequence of marked lines). See the :ref:`multi_line_exclude` section of the docs for more details and examples. - The JSON report now includes per-function and per-class coverage information. Thanks to `Daniel Diniz <pull 1809_>`\_ for getting the work started. This closes `issue 1793`\_ and `issue 1532`\_. - Fixed an incorrect calculation of "(no class)" lines in the HTML classes report. - Python 3.13.0b3 is supported. .. \_issue 118: [#&#8203;118](https://redirect.github.com/coveragepy/coveragepy/issues/118) .. \_issue 996: [#&#8203;996](https://redirect.github.com/coveragepy/coveragepy/issues/996) .. \_issue 1532: [#&#8203;1532](https://redirect.github.com/coveragepy/coveragepy/issues/1532) .. \_issue 1741: [#&#8203;1741](https://redirect.github.com/coveragepy/coveragepy/issues/1741) .. \_issue 1793: [#&#8203;1793](https://redirect.github.com/coveragepy/coveragepy/issues/1793) .. \_issue 1803: [#&#8203;1803](https://redirect.github.com/coveragepy/coveragepy/issues/1803) .. \_pull 1807: [#&#8203;1807](https://redirect.github.com/coveragepy/coveragepy/pull/1807) .. \_pull 1809: [#&#8203;1809](https://redirect.github.com/coveragepy/coveragepy/pull/1809) .. \_changes\_7-5-4: ### [`v7.5.4`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-754--2024-06-22) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.5.3...7.5.4) - If you attempt to combine statement coverage data with branch coverage data, coverage.py used to fail with the message "Can't combine arc data with line data" or its reverse, "Can't combine line data with arc data." These messages used internal terminology, making it hard for people to understand the problem. They are now changed to mention "branch coverage data" and "statement coverage data." - Fixed a minor branch coverage problem with wildcard match/case cases using names or guard clauses. - Started testing on 3.13 free-threading (nogil) builds of Python. I'm not claiming full support yet. Closes `issue 1799`\_. .. \_issue 1799: [#&#8203;1799](https://redirect.github.com/coveragepy/coveragepy/issues/1799) .. \_changes\_7-5-3: ### [`v7.5.3`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-753--2024-05-28) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.5.2...7.5.3) - Performance improvements for combining data files, especially when measuring line coverage. A few different quadratic behaviors were eliminated. In one extreme case of combining 700+ data files, the time dropped from more than three hours to seven minutes. Thanks for Kraken Tech for funding the fix. - Performance improvements for generating HTML reports, with a side benefit of reducing memory use, closing `issue 1791`\_. Thanks to Daniel Diniz for helping to diagnose the problem. .. \_issue 1791: [#&#8203;1791](https://redirect.github.com/coveragepy/coveragepy/issues/1791) .. \_changes\_7-5-2: ### [`v7.5.2`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-752--2024-05-24) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.5.1...7.5.2) - Fix: nested matches of exclude patterns could exclude too much code, as reported in `issue 1779`\_. This is now fixed. - Changed: previously, coverage.py would consider a module docstring to be an executable statement if it appeared after line 1 in the file, but not executable if it was the first line. Now module docstrings are never counted as executable statements. This can change coverage.py's count of the number of statements in a file, which can slightly change the coverage percentage reported. - In the HTML report, the filter term and "hide covered" checkbox settings are remembered between viewings, thanks to `Daniel Diniz <pull 1776_>`\_. - Python 3.13.0b1 is supported. - Fix: parsing error handling is improved to ensure bizarre source files are handled gracefully, and to unblock oss-fuzz fuzzing, thanks to `Liam DeVoe <pull 1788_>`*. Closes `issue 1787`*. .. \_pull 1776: [#&#8203;1776](https://redirect.github.com/coveragepy/coveragepy/pull/1776) .. \_issue 1779: [#&#8203;1779](https://redirect.github.com/coveragepy/coveragepy/issues/1779) .. \_issue 1787: [#&#8203;1787](https://redirect.github.com/coveragepy/coveragepy/issues/1787) .. \_pull 1788: [#&#8203;1788](https://redirect.github.com/coveragepy/coveragepy/pull/1788) .. \_changes\_7-5-1: </details> --- ### Configuration 📅 **Schedule**: (in timezone Etc/UTC) - Branch creation - "every weekend" - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/canonical/rockcraft). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMDkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIwOS4wIiwidGFyZ2V0QnJhbmNoIjoiaG90Zml4LzEuNSIsImxhYmVscyI6WyJQUjogRGVwZW5kZW5jaWVzIl19-->