WeRoBot
WeRoBot copied to clipboard
build(deps): bump coverage from 5.3.1 to 6.4.3
Bumps coverage from 5.3.1 to 6.4.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.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
andskip_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.4.3 — 2022-08-06
Fix a failure when combining data files if the file names contained glob-like patterns (
pull 1405
_). Thanks, Michael Krebs and Benjamin Schubert.Fix a messaging failure when combining Windows data files on a different drive than the current directory. (
pull 1430
, fixingissue 1428
). Thanks, Lorenzo Micò.Fix path calculations when running in the root directory, as you might do in a Docker container:
pull 1403
_, thanks Arthur Rio.Filtering in the HTML report wouldn't work when reloading the index page. This is now fixed (
pull 1413
_). Thanks, Marc Legendre.Fix a problem with Cython code measurement (
pull 1347
, fixingissue 972
). Thanks, Matus Valo... _issue 972: nedbat/coveragepy#972 .. _pull 1347: nedbat/coveragepy#1347 .. _pull 1403: nedbat/coveragepy#1403 .. _pull 1405: nedbat/coveragepy#1405 .. _pull 1413: nedbat/coveragepy#1413 .. _issue 1428: nedbat/coveragepy#1428 .. _pull 1430: nedbat/coveragepy#1430
.. _changes_6-4-2:
Version 6.4.2 — 2022-07-12
Updated for a small change in Python 3.11.0 beta 4: modules now start with a line with line number 0, which is ignored. This line cannnot be executed, so coverage totals were thrown off. This line is now ignored by coverage.py, but this also means that truly empty modules (like
__init__.py
) have no lines in them, rather than one phantom line. Fixesissue 1419
_.Internal debugging data added to sys.modules is now an actual module, to avoid confusing code that examines everything in sys.modules. Thanks, Yilei Yang (
pull 1399
_)... _pull 1399: nedbat/coveragepy#1399 .. _issue 1419: nedbat/coveragepy#1419
.. _changes_6-4-1:
... (truncated)
Commits
85a49ef
docs: latest sample1da23c5
docs: prep for 6.4.3616d963
docs: better wording in CHANGES0915b96
docs: correct a reference42202a8
docs: keep CHANGES up to date41602b5
fix: paths were wrong when running from root (#1403)eaf5592
test: add a test for #140536f508f
fix: filenames can contain special glob characters (#1405)774c364
doc: keep CHANGES up to date070d61c
fix(html): trigger filter on page load (#1413)- 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)