Bump coverage from 5.3.1 to 6.3

[dependabot[bot]]

Bumps coverage from 5.3.1 to 6.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:
  • Coverage will no longer report about other people’s code (issue 876). This is true even when using --source=. with a venv in the current directory.
  • Coverage will no longer generate “Already imported a file that will be measured” warnings about coverage itself (issue 905).
• 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.

coverage-5.5

• coverage combine has a new option, --keep to keep the original data files after combining them. The default is still to delete the files after they have been combined. This was requested in issue 1108 and implemented in pull request 1110. Thanks, Éric Larivière.
• When reporting missing branches in coverage report, branches aren’t reported that jump to missing lines. This adds to the long-standing behavior of not reporting branches from missing lines. Now branches are only reported if both the source and destination lines are executed. Closes both issue 1065 and issue 955.
• Minor improvements to the HTML report:
  • The state of the line visibility selector buttons is saved in local storage so you don’t have to fiddle with them so often, fixing issue 1123.
  • It has a little more room for line numbers so that 4-digit numbers work well, fixing issue 1124.
• Improved the error message when combining line and branch data, so that users will be more likely to understand what’s happening, closing issue 803.

coverage-5.4

• The text report produced by coverage report now always outputs a TOTAL line, even if only one Python file is reported. This makes regex parsing of the output easier. Thanks, Judson Neer. This had been requested a number of times (issue 1086, issue 922, issue 732).
• The skip_covered and skip_empty settings in the configuration file can now be specified in the [html] section, so that text reports and HTML reports can use separate settings. The HTML report will still use the [report] settings if there isn’t a value in the [html] section. Closes issue 1090.
• Combining files on Windows across drives now works properly, fixing issue 577. Thanks, Valentin Lab.
• Fix an obscure warning from deep in the _decimal module, as reported in issue 1084.
• Update to support Python 3.10 alphas in progress, including PEP 626: Precise line numbers for debugging and other tools.

Changelog

Sourced from coverage's changelog.

Version 6.3 — 2022-01-25

• Feature: Added the lcov command to generate reports in LCOV format. Thanks, Bradley Burns <pull 1289_>. Closes issues 587 <issue 587_> and 626 <issue 626_>_.

• Feature: the coverage data file can now be specified on the command line with the --data-file option in any command that reads or writes data. This is in addition to the existing COVERAGE_FILE environment variable. Closes issue 624. Thanks, Nikita Bloshchanevich <pull 1304_>.

• Feature: coverage measurement data will now be written when a SIGTERM signal is received by the process. This includes :meth:Process.terminate <python:multiprocessing.Process.terminate>, and other ways to terminate a process. Currently this is only on Linux and Mac; Windows is not supported. Fixes issue 1307_.

• Dropped support for Python 3.6, which reached end-of-life on 2021-12-23.

• Updated Python 3.11 support to 3.11.0a4, fixing issue 1294_.

• Fix: the coverage data file is now created in a more robust way, to avoid problems when multiple processes are trying to write data at once. Fixes issues 1303 <issue 1303_>_ and 883 <issue 883_>_.

• Fix: a .gitignore file will only be written into the HTML report output directory if the directory is empty. This should prevent certain unfortunate accidents of writing the file where it is not wanted.

• Releases now have MacOS arm64 wheels for Apple Silicon, fixing issue 1288_.

.. _issue 587: nedbat/coveragepy#587 .. _issue 624: nedbat/coveragepy#624 .. _issue 626: nedbat/coveragepy#626 .. _issue 883: nedbat/coveragepy#883 .. _issue 1288: nedbat/coveragepy#1288 .. _issue 1294: nedbat/coveragepy#1294 .. _issue 1303: nedbat/coveragepy#1303 .. _issue 1307: nedbat/coveragepy#1307 .. _pull 1289: nedbat/coveragepy#1289 .. _pull 1304: nedbat/coveragepy#1304

.. _changes_62:

Version 6.2 — 2021-11-26

• Feature: Now the --concurrency setting can now have a list of values, so

... (truncated)

Commits

• 7d9d300 build: 'pypy' is pypy-3.6, which we don't support anymore
• 97d78e6 build: prepping for 6.3
• fb3f632 docs: latest sample HTML report
• 2e65e19 docs: make it easier to add command-line options correctly
• bf8cbe1 fix: more cleanup of --data-file options
• f9a5451 docs: touch up the changelog
• 2ff2439 style: uniform formatting of cmdline options
• 1a75ebb refactor: adjust some of the --data-file option handling
• ba884e4 feat: use --data-file to configure the coverage database
• cfe14c2 build: stop deleting 3.9 muslinux wheels, because they are ok now. #1268
• 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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #66.