Sourced from coverage's changelog.
Version 7.13.5 — 2026-03-17
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 toEllie Ayla <pull 2142_>.Fix: the C extension wouldn't build on VS2019, but now it does (
issue 2145_)... _issue 2138: coveragepy/coveragepy#2138 .. _issue 2141: coveragepy/coveragepy#2141 .. _pull 2142: coveragepy/coveragepy#2142 .. _issue 2145: coveragepy/coveragepy#2145
.. _changes_7-13-4: