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.15.4` → `==7.16.0` |  |  | --- ### Release Notes <details> <summary>coveragepy/coveragepy (coverage)</summary> ### [`v7.16.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7160--2026-08-28) [Compare Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.15.4...7.16.0) - When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define `[paths]` configuration to combine data across operating systems. Fixes `issue 2266`\_. - The :meth:`.Coverage.switch_context` method now returns the previous context. - Fix: previously, a `[paths]` pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in `pull 2268`\_. - Fixes to validation of options and configuration settings: - Negative precision settings now always cause useful error messages (`pull 2261`\_). - An invalid regex in the `--contexts` option (or the `[report] contexts` setting) reported a confusing "Couldn't use data file ...: user-defined function raised exception" error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (`pull 2262`\_). - Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren't strings (like `omit`, `exclude_lines`, or a `[paths]` entry), file settings like `data_file`, and any wrong-typed value in the `[paths]` section (`pull 2263`\_). - `coverage run` refuses run-affecting command-line options like `--branch` alongside `--concurrency=multiprocessing`, since they can't reach the subprocesses. The check only recognized `multiprocessing` as the entire option value, so `--concurrency=multiprocessing,thread` slipped through and failed later with "Can't combine statement coverage data with branch data". Each named concurrency library is now properly considered (`pull 2270`\_). - Fix: `coverage annotate -d DIR` raised an `AssertionError` if any measured file had an extension other than `.py`, such as a `.pyw` file on Windows. The original extension is now restored on the annotated copy (`pull 2265`\_). .. \_pull 2261: [#&#8203;2261](https://redirect.github.com/coveragepy/coveragepy/pull/2261) .. \_pull 2262: [#&#8203;2262](https://redirect.github.com/coveragepy/coveragepy/pull/2262) .. \_pull 2263: [#&#8203;2263](https://redirect.github.com/coveragepy/coveragepy/pull/2263) .. \_pull 2265: [#&#8203;2265](https://redirect.github.com/coveragepy/coveragepy/pull/2265) .. \_issue 2266: [#&#8203;2266](https://redirect.github.com/coveragepy/coveragepy/issues/2266) .. \_pull 2268: [#&#8203;2268](https://redirect.github.com/coveragepy/coveragepy/pull/2268) .. \_pull 2270: [#&#8203;2270](https://redirect.github.com/coveragepy/coveragepy/pull/2270) .. \_changes\_7-15-4: </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:eyJjcmVhdGVkSW5WZXIiOiI0NC42MS4zIiwidXBkYXRlZEluVmVyIjoiNDQuNjEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUFI6IERlcGVuZGVuY2llcyJdfQ==-->