chore(deps): update dependency coverage to v4.5.4 #4276
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==4.3.4
->==4.5.4
Release Notes
nedbat/coveragepy (coverage)
v4.5.4
Compare Source
Version 4.5.4 — 2019-07-29
➡️ PyPI page: coverage 4.5.4.
➡️ To install:
python3 -m pip install coverage==4.5.4
v4.5.3
: 4.5.3Compare Source
Version 4.5.3 — 2019-03-09
➡️ PyPI page: coverage 4.5.3.
➡️ To install:
python3 -m pip install coverage==4.5.3
v4.5.2
: 4.5.2Compare Source
Version 4.5.2 — 2018-11-12
➡️ PyPI page: coverage 4.5.2.
➡️ To install:
python3 -m pip install coverage==4.5.2
v4.5.1
: 4.5.1Compare Source
Version 4.5.1 — 2018-02-10
[run] omit
and[report] omit
settings, an old bug has become apparent. If you specified a package name for[run] source
, then omit patterns weren’t matched inside that package. This bug (issue 638) is now fixed.--debug=sys
.➡️ PyPI page: coverage 4.5.1.
➡️ To install:
python3 -m pip install coverage==4.5.1
v4.5
: 4.5Compare Source
Version 4.5 — 2018-02-03
fail_under
option can now be a float. Note that you must specify the[report] precision
configuration option for the fractional part to be used. Thanks to Lars Hupfeldt Nielsen for help with the implementation. Fixes issue 631.include
andomit
options can be specified for both the[run]
and[report]
phases of execution. 4.4.2 introduced some incorrect interactions between those phases, where the options for one were confused for the other. This is now corrected, fixing issue 621 and issue 622. Thanks to Daniel Hahler for seeing more clearly than I could.coverage combine
command used to always overwrite the data file, even when no data had been read from apparently combinable files. Now, an error is raised if we thought there were files to combine, but in fact none of them could be used. Fixes issue 629.coverage combine
command could get confused about path separators when combining data collected on Windows with data collected on Linux, as described in issue 618. This is now fixed: the result path always uses the path separator specified in the[paths]
result.➡️ PyPI page: coverage 4.5.
➡️ To install:
python3 -m pip install coverage==4.5
v4.4.2
: 4.4.2Compare Source
Version 4.4.2 — 2017-11-05
--source
and--include
no longer silently ignores the include setting, instead it displays a warning. Thanks, Loïc Dachary. Closes issue 265 and issue 101.➡️ PyPI page: coverage 4.4.2.
➡️ To install:
python3 -m pip install coverage==4.4.2
v4.4.1
: 4.4.1Compare Source
Version 4.4.1 — 2017-05-14
➡️ PyPI page: coverage 4.4.1.
➡️ To install:
python3 -m pip install coverage==4.4.1
v4.4
Compare Source
Fix: in some cases, even with
[run] relative_files=True
, a data filecould be created with absolute path names. When combined with other relative
data files, it was random whether the absolute file names would be made
relative or not. If they weren't, then a file would be listed twice in
reports, as detailed in
issue 1752
_. This is now fixed: absolute filenames are always made relative when combining. Thanks to Bruno Rodrigues dos
Santos for support.
Fix: the last case of a match/case statement had an incorrect message if the
branch was missed. It said the pattern never matched, when actually the
branch is missed if the last case always matched.
Fix: clicking a line number in the HTML report now positions more accurately.
Fix: the
report:format
setting was defined as a boolean, but should be astring. Thanks,
Tanaydin Sirin <pull 1754_>
_. It is also now documentedon the :ref:
configuration page <config_report_format>
... _issue 1752:https://github.com/nedbat/coveragepy/issues/17522
.. _pull 1754https://github.com/nedbat/coveragepy/pull/175454
.. _changes_7-4-3:
Configuration
📅 Schedule: Branch creation - "after 5am on saturday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.