Bump coverage from 5.5 to 7.2.3
Bumps coverage from 5.5 to 7.2.3.
Release notes
Sourced from coverage's releases.
coverage-5.6b1
- Third-party packages are now ignored in coverage reporting. This solves a few problems:
- The HTML report uses j/k to move up and down among the highlighted chunks of code. They used to highlight the current chunk, but 5.0 broke that behavior. Now the highlighting is working again.
- The JSON report now includes
percent_covered_display, a string with the total percentage, rounded to the same number of decimal places as the other reports’ totals.
Changelog
Sourced from coverage's changelog.
Version 7.2.3 — 2023-04-06
Fix: the :ref:
config_run_sigtermsetting was meant to capture data if a process was terminated with a SIGTERM signal, but it didn't always. This was fixed thanks toLewis Gaul <pull 1600_>, closingissue 1599.Performance: HTML reports with context information are now much more compact. File sizes are typically as small as one-third the previous size, but can be dramatically smaller. This closes
issue 1584_ thanks toOleh Krehel <pull 1587_>_.Development dependencies no longer use hashed pins, closing
issue 1592_... _issue 1584: nedbat/coveragepy#1584 .. _pull 1587: nedbat/coveragepy#1587 .. _issue 1592: nedbat/coveragepy#1592 .. _issue 1599: nedbat/coveragepy#1599 .. _pull 1600: nedbat/coveragepy#1600
.. _changes_7-2-2:
Version 7.2.2 — 2023-03-16
Fix: if a virtualenv was created inside a source directory, and a sourced package was installed inside the virtualenv, then all of the third-party packages inside the virtualenv would be measured. This was incorrect, but has now been fixed: only the specified packages will be measured, thanks to
Manuel Jacob <pull 1560_>_.Fix: the
coverage lcovcommand could create a .lcov file with incorrect LF (lines found) and LH (lines hit) totals. This is now fixed, thanks toIan Moore <pull 1583_>_.Fix: the
coverage xmlcommand on Windows could create a .xml file with duplicate<package>elements. This is now fixed, thanks toBenjamin Parzella <pull 1574_>, closingissue 1573... _pull 1560: nedbat/coveragepy#1560 .. _issue 1573: nedbat/coveragepy#1573 .. _pull 1574: nedbat/coveragepy#1574 .. _pull 1583: nedbat/coveragepy#1583
.. _changes_7-2-1:
Version 7.2.1 — 2023-02-26
... (truncated)
Commits
6297f19docs: sample HTML for 7.2.38cb979bdocs: prep for 7.2.36d5c4d4docs: add the fix for #1599, thanks Lewis Gaulf27c9cafix: save coverage data on SIGTERM (#1600)3bc7d2cchore: make upgradeacd1e03docs: more tweaking of the gold-file instructionsb8498bfperf: make the context shortcodes even shorter80b4794build: update .git-blame-ignore-revsb03ab92style: use double-quotes in JavaScript36d0104chore: make upgrade to remove hashes- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)