← Back to issue list

build(deps): update dependency coverage to v7.12.0 (main)

View original Github issue

Metadata

Project
craft-cli
Number
#403
Type
pull request
State
merged
Author
renovate[bot]
Labels
PR: Dependencies
Created
Updated
Closed

Current evaluation

Renovate PR merged as commit 79f1a8c, bumping coverage from 7.11.0 to 7.12.0 in two dependency files; all CI checks passed and 2 reviewers approved.

Resolution: closed resolved

Reason: The PR itself was merged into main as commit 79f1a8c ("build(deps): update dependency coverage to v7.12.0 (#403)"), changing coverage==7.11.0 to ==7.12.0. Later bumps (#406, #431, #450, #459, #469, #482) moved coverage forward to 7.16.0.

Evaluated by: mr-cal-bot

No scores available.

Issue body

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.11.0` -> `==7.12.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/coverage/7.12.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/coverage/7.11.0/7.12.0?slim=true) | --- ### Release Notes <details> <summary>coveragepy/coveragepy (coverage)</summary> ### [`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: </details> --- ### Configuration 📅 **Schedule**: Branch creation - "every weekend" in timezone Etc/UTC, 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/craft-cli). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi4zMi4yIiwidXBkYXRlZEluVmVyIjoiNDIuMzIuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUFI6IERlcGVuZGVuY2llcyJdfQ==-->

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Renovate PR merged as commit 79f1a8c, bumping coverage from 7.11.0 to 7.12.0 in two dependency files; all CI checks passed and 2 reviewers approved.
stealth/space-bunny-alpha — closed resolved Merged in #403 as 79f1a8c, updating coverage from 7.11.0 to 7.12.0 across two files after all CI checks passed and two reviewers approved.
qwen/qwen3.6-35b-a3b — — Merged automated dependency update for coverage from v7.11.0 to v7.12.0 on main. Approved by two reviewers, passed all CI checks, and successfully merged via Renovate.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-cli#406 (confidence 70%)

    Follow-up Renovate bump of coverage to 7.13.0 (commit bed5a10), superseding the 7.12.0 pin.

  • Related To: canonical/craft-cli#397 (confidence 60%)

    Preceding coverage bump to 7.11.0 (commit f4f339d) that this PR updated.

Related issues

Issue Project State Summary Similarity
#397 build(deps): update dependency coverage to v7.11.0 (main) craft-cli merged Renovate PR #397 merged into main as commit f4f339d, bumping the coverage test dependency from 7.10.6 to 7.11.0 (which also picked up 7.10.7's performance fixes). All CI checks passed with 2 approvals.
94%
#310 build(deps): update dependency coverage to v7.10.4 (main) craft-store merged Renovate PR bumping the coverage dev dependency from 7.6.2 to 7.10.4 was approved by two reviewers and merged to main as commit 4f30eec (later followed by #329, #335, #347, #367).
93%
#431 build(deps): update dependency coverage to v7.13.5 (main) craft-cli merged Merged into main via PR #431 (commit 63aca76), updating coverage from 7.13.4 to 7.13.5 after all CI checks passed.
92%
#690 build(deps): update dependency coverage to v7.6.3 (main) craft-providers merged Renovate PR #690 was merged, updating coverage from 7.6.2 to 7.6.3 via commit 5631cfa.
92%
#384 build(deps): update dependency coverage to v7.10.6 craft-cli merged Renovate PR #384 bumped the dev dependency coverage from 7.6.1 to 7.10.6; approved by 2 reviewers and merged to main as commit 6d467a1. Later superseded by coverage updates in #397, #403, #406, #431, #450, #459, #469 and #482 (now 7.16.1).
92%
#482 build(deps): update dependency coverage to v7.16.0 (main) craft-cli merged Renovate dependency bump of coverage 7.15.4 → 7.16.0 was approved and merged into main as commit 5873370, with all 48 CI checks passing (2 files, +126/-126).
91%
#406 build(deps): update dependency coverage to v7.13.0 (main) craft-cli merged Renovate PR #406 merged (commit bed5a10), bumping coverage from 7.12.0 to 7.13.0 in main; later superseded by #431, #450, #459, #469, #482.
91%
#450 build(deps): update dependency coverage to v7.14.2 (main) craft-cli merged Renovate PR #450 bumping coverage from 7.13.5 to 7.14.2 was approved and merged as commit ad6c9a0, updating the pin in two files (changelog/constraints) with all CI checks passing.
91%
#367 build(deps): update dependency coverage to v7.14.0 (main) craft-store merged Merged PR #367 into main, upgrading coverage from 7.13.5 to 7.14.0 in commit 905fea0.
90%
#629 build(deps): update dependency coverage to v7.6.1 craft-providers merged Merged Renovate PR #629 updated coverage from 7.5.1 to 7.6.1; the dependency bump landed in commit ba02988.
87%