Bump coverage[toml] from 7.5.0 to 7.6.0

[dependabot]

Bumps coverage[toml] from 7.5.0 to 7.6.0.

Release notes

Sourced from coverage[toml]'s releases.

7.6.0

[WARNING] Reference not found for 'daniel diniz ' at /var/folders/6j/khn0mcrj35d1k3yylpl8zl080000gn/T/scriv_rst_fg1z3eh9_chunk line 2 column 9

• Exclusion patterns can now be multi-line, thanks to Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including those requested in issues 118 (entire files), 996 (multiple lines only when appearing together), 1741 (remainder of a function), and 1803 (arbitrary sequence of marked lines). See the multi_line_exclude section of the docs for more details and examples.
• The JSON report now includes per-function and per-class coverage information. Thanks to Daniel Diniz for getting the work started. This closes issue 1793 and issue 1532.
• Fixed an incorrect calculation of "(no class)" lines in the HTML classes report.
• Python 3.13.0b3 is supported.

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

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

Changelog

Sourced from coverage[toml]'s changelog.

Version 7.6.0 — 2024-07-11

• Exclusion patterns can now be multi-line, thanks to Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including those requested in issues 118 <issue 118_> (entire files), 996 <issue 996_>_ (multiple lines only when appearing together), 1741 <issue 1741_>_ (remainder of a function), and 1803 <issue 1803_>_ (arbitrary sequence of marked lines). See the :ref:multi_line_exclude section of the docs for more details and examples.

• The JSON report now includes per-function and per-class coverage information. Thanks to Daniel Diniz <pull 1809_>_ for getting the work started. This closes issue 1793_ and issue 1532_.

• Fixed an incorrect calculation of "(no class)" lines in the HTML classes report.

• Python 3.13.0b3 is supported.

.. _issue 118: nedbat/coveragepy#118 .. _issue 996: nedbat/coveragepy#996 .. _issue 1532: nedbat/coveragepy#1532 .. _issue 1741: nedbat/coveragepy#1741 .. _issue 1793: nedbat/coveragepy#1793 .. _issue 1803: nedbat/coveragepy#1803 .. _pull 1807: nedbat/coveragepy#1807 .. _pull 1809: nedbat/coveragepy#1809

.. _changes_7-5-4:

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

... (truncated)

Commits

• 59a3cd7 docs: sample HTML for 7.6.0
• 7f27fa7 docs: prep for 7.6.0
• 6a268b0 docs: issues closed by the json region reporting
• 5bfe9e7 chore: bump actions/setup-python from 5.1.0 to 5.1.1 (#1814)
• ab609ef docs: mention json region reporting in the changes
• 92d96b9 fix: json report needs 'no class' and 'no function' also
• e47e7e7 refactor: move duplicate code into methods
• 3d6be2b fix: json format should bump for regions
• a9992d2 test: add a test of json regions with branches
• 8b89764 test: json expectations should have explicit format number
• 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)