Bump coverage[toml] from 7.4.4 to 7.5.4

[dependabot]

Bumps coverage[toml] from 7.4.4 to 7.5.4.

Release notes

Sourced from coverage[toml]'s releases.

7.5.4

• 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.

➡️  PyPI page: coverage 7.5.4. :arrow_right:  To install: python3 -m pip install coverage==7.5.4

7.5.3

• 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 for helping to diagnose the problem.

➡️  PyPI page: coverage 7.5.3. :arrow_right:  To install: python3 -m pip install coverage==7.5.3

7.5.2

• 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.
• 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. Closes issue 1787.

➡️  PyPI page: coverage 7.5.2. :arrow_right:  To install: python3 -m pip install coverage==7.5.2

7.5.1

• 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 by Daniel Diniz.
• Fix: very complex source files like this one could cause 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.

➡️  PyPI page: coverage 7.5.1. :arrow_right:  To install: python3 -m pip install coverage==7.5.1

7.5.0

• 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.

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

Version 7.5.4 — 2024-06-22

• 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: nedbat/coveragepy#1799

.. _changes_7-5-3:

Version 7.5.3 — 2024-05-28

• 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 for helping to diagnose the problem.

.. _issue 1791: nedbat/coveragepy#1791

.. _changes_7-5-2:

Version 7.5.2 — 2024-05-24

• 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.

... (truncated)

Commits

• 22c09c6 docs: sample HTML for 7.5.4
• 9e16381 docs: prep for 7.5.4
• fba9b9e docs: link issue 1799 from the changelog
• f124de8 build: no longer download kits to upload them
• 9516cf6 build: hash-pin all actions
• c6e0985 build: finish up the publish action
• 4a49458 build: get the latest dist run id for publishing
• fb15efa build: pin hashes for publishing actions
• c20af95 build: use the correct item: github.event.action
• ccbab15 build: dump all the github actions data
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)