chore(deps): update dependency coverage to v7.5.4 #12
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
renovate
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: olofvndrhr/octodns-netbox-dns#12
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/coverage-7.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==7.4.2
->==7.5.4
Release Notes
nedbat/coveragepy (coverage)
v7.5.4
Compare Source
If you attempt to combine statement coverage data with branch coverage data,
coverage.py used to fail with the message "Can't combine arc data with line
data" or its reverse, "Can't combine line data with arc data." These
messages used internal terminology, making it hard for people to understand
the problem. They are now changed to mention "branch coverage data" and
"statement coverage data."
Fixed a minor branch coverage problem with wildcard match/case cases using
names or guard clauses.
Started testing on 3.13 free-threading (nogil) builds of Python. I'm not
claiming full support yet. Closes
issue 1799
_... _issue 1799: https://github.com/nedbat/coveragepy/issues/1799
.. _changes_7-5-3:
v7.5.3
Compare Source
Performance improvements for combining data files, especially when measuring
line coverage. A few different quadratic behaviors were eliminated. In one
extreme case of combining 700+ data files, the time dropped from more than
three hours to seven minutes. Thanks for Kraken Tech for funding the fix.
Performance improvements for generating HTML reports, with a side benefit of
reducing memory use, closing
issue 1791
_. Thanks to Daniel Diniz forhelping to diagnose the problem.
.. _issue 1791: https://github.com/nedbat/coveragepy/issues/1791
.. _changes_7-5-2:
v7.5.2
Compare Source
Fix: nested matches of exclude patterns could exclude too much code, as
reported in
issue 1779
_. This is now fixed.Changed: previously, coverage.py would consider a module docstring to be an
executable statement if it appeared after line 1 in the file, but not
executable if it was the first line. Now module docstrings are never counted
as executable statements. This can change coverage.py's count of the number
of statements in a file, which can slightly change the coverage percentage
reported.
In the HTML report, the filter term and "hide covered" checkbox settings are
remembered between viewings, thanks to
Daniel Diniz <pull 1776_>
_.Python 3.13.0b1 is supported.
Fix: parsing error handling is improved to ensure bizarre source files are
handled gracefully, and to unblock oss-fuzz fuzzing, thanks to
Liam DeVoe <pull 1788_>
. Closesissue 1787
... _pull 1776: https://github.com/nedbat/coveragepy/pull/1776
.. _issue 1779: https://github.com/nedbat/coveragepy/issues/1779
.. _issue 1787: https://github.com/nedbat/coveragepy/issues/1787
.. _pull 1788: https://github.com/nedbat/coveragepy/pull/1788
.. _changes_7-5-1:
v7.5.1
Compare Source
Fix: a pragma comment on the continuation lines of a multi-line statement
now excludes the statement and its body, the same as if the pragma is
on the first line. This closes
issue 754
. The fix was contributed byDaniel Diniz <pull 1773_>
.Fix: very complex source files like
this one <resolvent_lookup_>
_ couldcause a maximum recursion error when creating an HTML report. This is now
fixed, closing
issue 1774
_.HTML report improvements:
Support files (JavaScript and CSS) referenced by the HTML report now have
hashes added to their names to ensure updated files are used instead of
stale cached copies.
Missing branch coverage explanations that said "the condition was never
false" now read "the condition was always true" because it's easier to
understand.
Column sort order is remembered better as you move between the index pages,
fixing
issue 1766
. Thanks,Daniel Diniz <pull 1768_>
... _resolvent_lookup:
130950f3e6/sympy/polys/numberfields/resolvent_lookup.py
.. _issue 754: https://github.com/nedbat/coveragepy/issues/754
.. _issue 1766: https://github.com/nedbat/coveragepy/issues/1766
.. _pull 1768: https://github.com/nedbat/coveragepy/pull/1768
.. _pull 1773: https://github.com/nedbat/coveragepy/pull/1773
.. _issue 1774: https://github.com/nedbat/coveragepy/issues/1774
.. _changes_7-5-0:
v7.5.0
Compare Source
Added initial support for function and class reporting in the HTML report.
There are now three index pages which link to each other: files, functions,
and classes. Other reports don't yet have this information, but it will be
added in the future where it makes sense. Feedback gladly accepted!
Finishes
issue 780
_.Other HTML report improvements:
There is now a "hide covered" checkbox to filter out 100% files, finishing
issue 1384
_.The index page is always sorted by one of its columns, with clearer
indications of the sorting.
The "previous file" shortcut key didn't work on the index page, but now it
does, fixing
issue 1765
_.The debug output showing which configuration files were tried now shows
absolute paths to help diagnose problems where settings aren't taking effect,
and is renamed from "attempted_config_files" to the more logical
"config_files_attempted."
Python 3.13.0a6 is supported.
.. _issue 780: https://github.com/nedbat/coveragepy/issues/780
.. _issue 1384: https://github.com/nedbat/coveragepy/issues/1384
.. _issue 1765: https://github.com/nedbat/coveragepy/issues/1765
.. _changes_7-4-4:
v7.4.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/1752
.. _pull 1754: https://github.com/nedbat/coveragepy/pull/1754
.. _changes_7-4-3:
v7.4.3
Compare Source
size during iteration." This is now fixed, closing
issue 1733
_... _issue 1733: https://github.com/nedbat/coveragepy/issues/1733
.. _changes_7-4-2:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
d2579b3dba
to39c179af70
Update dependency coverage to v7.4.3to chore(deps): update dependency coverage to v7.4.339c179af70
to1cbd26d4cb
chore(deps): update dependency coverage to v7.4.3to chore(deps): update dependency coverage to v7.4.41cbd26d4cb
to39b5883b21
39b5883b21
to728316f0e8
chore(deps): update dependency coverage to v7.4.4to chore(deps): update dependency coverage to v7.5.0728316f0e8
tof9e34fb714
f9e34fb714
to8e409e4542
chore(deps): update dependency coverage to v7.5.0to chore(deps): update dependency coverage to v7.5.18e409e4542
tocd6653d7c6
chore(deps): update dependency coverage to v7.5.1to chore(deps): update dependency coverage to v7.5.2cd6653d7c6
tof857190014
chore(deps): update dependency coverage to v7.5.2to chore(deps): update dependency coverage to v7.5.3f857190014
toe50defd5c8
chore(deps): update dependency coverage to v7.5.3to chore(deps): update dependency coverage to v7.5.4e50defd5c8
toc4e11f91aa
Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.