← Back to issue list

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

View original Github issue

Metadata

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

Current evaluation

Merged automated dependency update for coverage from v7.13.1 to v7.13.5. Approved by two reviewers, passed CI checks, and merged into main.

Suggested action:

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.13.1` → `==7.13.5` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/coverage/7.13.5?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/coverage/7.13.1/7.13.5?slim=true) | --- ### Release Notes <details> <summary>coveragepy/coveragepy (coverage)</summary> ### [`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: </details> --- ### Configuration 📅 **Schedule**: Branch creation - "every weekend" in timezone Etc/UTC, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, 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-store). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My42Ni40IiwidXBkYXRlZEluVmVyIjoiNDMuNjYuNCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUFI6IERlcGVuZGVuY2llcyJdfQ==-->

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Merged automated dependency update for coverage from v7.13.1 to v7.13.5. Approved by two reviewers, passed CI checks, and merged into main.
qwen3.6-35b-a3b-mtp-q6 Automatically merged dependency update upgrading coverage from v7.13.1 to v7.13.5. Includes fixes for memory leaks, markdown escaping, and VS2019 builds. Applied to main via Renovate automerge.

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 Merged automated dependency update upgrading coverage from v7.12.0 to v7.13.0. Approved by two reviewers and passed all CI checks before merging into the main branch.
99%
#469 build(deps): update dependency coverage to v7.15.4 (main) craft-cli merged Merged automated dependency update for coverage from v7.15.2 to v7.15.4. Approved by one reviewer, passed CI checks, and merged into main.
96%
#397 build(deps): update dependency coverage to v7.11.0 (main) craft-cli merged Merged automated dependency update for coverage from v7.10.6 to v7.11.0. Approved by two reviewers, passed all CI checks, and merged into main.
96%
#329 build(deps): update dependency coverage to v7.12.0 (main) craft-store merged Merged an automated dependency update upgrading coverage from v7.10.7 to v7.12.0. Approved by two reviewers and passing CI, the change was successfully integrated into the main branch.
96%
#406 build(deps): update dependency coverage to v7.13.0 (main) craft-cli merged Merged dependency update to coverage v7.13.0. The change passed all CI checks, received two approvals, and modifies two files to update the project configuration.
95%
#403 build(deps): update dependency coverage to v7.12.0 (main) craft-cli merged 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.
95%
#310 build(deps): update dependency coverage to v7.10.4 (main) craft-store merged Merged automated dependency update upgrading coverage from v7.6.2 to v7.10.4. The change passed all CI checks, received reviewer approval, and was successfully merged to main.
95%
#459 build(deps): update dependency coverage to v7.15.0 (main) craft-cli merged 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.
94%
#367 build(deps): update dependency coverage to v7.14.0 (main) craft-store merged Merged automated dependency update for coverage from v7.13.5 to v7.14.0. The pull request passed CI checks and was successfully merged into the main branch.
94%
#482 build(deps): update dependency coverage to v7.16.0 (main) craft-cli merged Merged automated dependency update upgrading coverage from v7.15.4 to v7.16.0. The change passed all CI checks, received reviewer approval, and was successfully merged into the main branch.
93%