build(deps): update dependency coverage to v7.15.0 (main)
Metadata
Current evaluation
Renovate dependency bump of coverage 7.14.2 → 7.15.0 in craft-cli was approved and merged via PR #459 (commit 5014730), with all CI checks passing.
Resolution: closed resolved
Reason: PR #459 was merged into main in commit 5014730, pinning coverage==7.15.0 after one approval; all listed test, lint and policy checks passed with no failures.
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.14.2` → `==7.15.0` |  |  |
---
### Release Notes
<details>
<summary>coveragepy/coveragepy (coverage)</summary>
### [`v7.15.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7150--2026-07-02)
[Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.14.3...7.15.0)
- Since 7.14.0, reporting commands implicitly combine parallel data files. Now
those commands have a new option `--keep-combined` to retain the data files
after combining them instead of the default, which is to delete them.
Finishes `issue 2198`\_.
- Fix: the LCOV report would incorrectly count excluded functions as uncovered,
as described in `issue 2205`*. This is now fixed thanks to `Martin Kuntz
Jacobsen <pull 2206_>`*.
- When running your program, coverage now correctly sets
`yourmodule.__spec__.loader` as `strongly recommended <--loader--_>`*,
avoiding the deprecation warning described in `issue 2208`*. Thanks, `A5rocks <pull 2209_>`\_.
- Fix: with Python 3.10, running with the `-I` (isolated mode) option didn't
correctly omit the current directory from the module search path, as
described in `issue 2103`*. That is now fixed thanks to `Ilia Sorokin <pull
2211_>`*.
.. *--loader--: <https://docs.python.org/3/reference/datamodel.html#module.__loader>*\_
.. \_issue 2103: [#​2103](https://redirect.github.com/coveragepy/coveragepy/issues/2103)
.. \_issue 2198: [#​2198](https://redirect.github.com/coveragepy/coveragepy/issues/2198)
.. \_issue 2205: [#​2205](https://redirect.github.com/coveragepy/coveragepy/issues/2205)
.. \_pull 2206: [#​2206](https://redirect.github.com/coveragepy/coveragepy/pull/2206)
.. \_issue 2208: [#​2208](https://redirect.github.com/coveragepy/coveragepy/issues/2208)
.. \_pull 2209: [#​2209](https://redirect.github.com/coveragepy/coveragepy/pull/2209)
.. \_pull 2211: [#​2211](https://redirect.github.com/coveragepy/coveragepy/pull/2211)
.. \_changes\_7-14-3:
### [`v7.14.3`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7143--2026-06-22)
[Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.14.2...7.14.3)
- Fix: the default `...` exclusion rule now also matches function bodies
whose closing return-type bracket is on its own line (for example, after a
long `-> dict[ ... ]` annotation that a formatter has split over multiple
lines). Closes `issue 2185`*, thanks `Mengjia Shang <pull 2196_>`*.
- Fix: On 3.13t, we incorrectly issued `Couldn't import C tracer` errors.
We can't import the C tracer because in 7.14.2 we stopped shipping compiled
wheels for 3.13t. Thanks, `Hugo van Kemenade <pull 2203_>`\_.
.. \_issue 2185: [#​2185](https://redirect.github.com/coveragepy/coveragepy/issues/2185)
.. \_pull 2196: [#​2196](https://redirect.github.com/coveragepy/coveragepy/pull/2196)
.. \_pull 2203: [#​2203](https://redirect.github.com/coveragepy/coveragepy/pull/2203)
.. \_changes\_7-14-2:
</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/craft-cli).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNDIuMiIsInVwZGF0ZWRJblZlciI6IjQzLjI0Mi4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJQUjogRGVwZW5kZW5jaWVzIl19-->
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Renovate dependency bump of coverage 7.14.2 → 7.15.0 in craft-cli was approved and merged via PR #459 (commit 5014730), with all CI checks passing. | |
| stealth/space-bunny-alpha | — | closed resolved | Renovate bumped coverage 7.14.2 → 7.15.0 in main; approved and merged as commit 5014730 with all CI checks passing. Pinned in test-requirements.txt and a constraints file. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged Renovate PR #459 in commit 5014730, updating coverage from 7.14.2 to 7.15.0 after approval and all reported CI checks passed. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged automated dependency update for coverage from v7.14.2 to v7.15.0 on main. The change was approved and passed all CI checks before merge. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged automated dependency update for coverage from v7.14.2 to v7.15.0 on the main branch. Generated by Renovate and applied cleanly without conflicts. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #335 build(deps): update dependency coverage to v7.13.0 (main) | craft-store | merged | Renovate dependency bump of coverage7.12.0 → 7.13.0 merged into craft-store main as commit 327b748; all CI checks green and approved by 2 reviewers. Later superseded by #347 (7.13.5) and #367 (7.14.0). | |
| #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). | |
| #396 build(deps): update dependency coverage to v7.11.0 (main) - autoclosed | craft-cli | closed | Autoclosed after the identical coverage 7.10.6→7.11.0 update landed through canonical/craft-cli#397 in commit f4f339d. | |
| #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. | |
| #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). | |
| #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). | |
| #403 build(deps): update dependency coverage to v7.12.0 (main) | craft-cli | merged | 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. | |
| #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. | |
| #329 build(deps): update dependency coverage to v7.12.0 (main) | craft-store | merged | Merged canonical/craft-store#329, upgrading coverage from 7.10.7 to 7.12.0 in main via commit 6b48176. | |
| #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. |