Bump coverage[toml] from 7.3.2 to 7.6.8

[dependabot]

Bumps coverage[toml] from 7.3.2 to 7.6.8.

Release notes

Sourced from coverage[toml]'s releases.

7.6.8

Version 7.6.8 — 2024-11-23

• Fix: the LCOV report code assumed that a branch line that took no branches meant that the entire line was unexecuted. This isn’t true in a few cases: the line might always raise an exception, or might have been optimized away. Fixes issue 1896.
• Fix: similarly, the HTML report will now explain that a line that jumps to none of its expected destinations must have always raised an exception. Previously, it would say something nonsensical like, “line 4 didn’t jump to line 5 because line 4 was never true, and it didn’t jump to line 7 because line 4 was always true.” This was also shown in issue 1896.

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

7.6.7

Version 7.6.7 — 2024-11-15

• Fix: ugh, the other assert from 7.6.5 can also be encountered in the wild, so it’s been restored to a conditional. Sorry for the churn.

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

7.6.6

Version 7.6.6 — 2024-11-15

• One of the new asserts from 7.6.5 caused problems in real projects, as reported in issue 1891. The assert has been removed.

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

7.6.5

Version 7.6.5 — 2024-11-14

• Fix: fine-tuned the exact Python version (3.12.6) when exiting from with statements changed how they traced. This affected whether people saw the fix for issue 1880.
• Fix: isolate our code more from mocking in the os module that in rare cases can cause bizarre behavior.
• Refactor: some code unreachable code paths in parser.py were changed to asserts. If you encounter any of these, please let me know!

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

7.6.4

Version 7.6.4 — 2024-10-20

• Fix: multi-line with statements could cause contained branches to be incorrectly marked as missing (issue 1880). This is now fixed.

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

7.6.3

Version 7.6.3 — 2024-10-13

• Fix: nested context managers could incorrectly be analyzed to flag a missing branch on the last context manager, as described in issue 1876. This is now fixed.
• Fix: the missing branch message about not exiting a module had an extra “didn’t,” as described in issue 1873. This is now fixed.

➡️  PyPI page: coverage 7.6.3.

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

Version 7.6.8 — 2024-11-23

• Fix: the LCOV report code assumed that a branch line that took no branches meant that the entire line was unexecuted. This isn't true in a few cases: the line might always raise an exception, or might have been optimized away. Fixes issue 1896_.

• Fix: similarly, the HTML report will now explain that a line that jumps to none of its expected destinations must have always raised an exception. Previously, it would say something nonsensical like, "line 4 didn't jump to line 5 because line 4 was never true, and it didn't jump to line 7 because line 4 was always true." This was also shown in issue 1896_.

.. _issue 1896: nedbat/coveragepy#1896

.. _changes_7-6-7:

Version 7.6.7 — 2024-11-15

• Fix: ugh, the other assert from 7.6.5 can also be encountered in the wild, so it's been restored to a conditional. Sorry for the churn.

.. _changes_7-6-6:

Version 7.6.6 — 2024-11-15

• One of the new asserts from 7.6.5 caused problems in real projects, as reported in issue 1891_. The assert has been removed.

.. _issue 1891: nedbat/coveragepy#1891

.. _changes_7-6-5:

Version 7.6.5 — 2024-11-14

• Fix: fine-tuned the exact Python version (3.12.6) when exiting from with statements changed how they traced. This affected whether people saw the fix for issue 1880_.

• Fix: isolate our code more from mocking in the os module that in rare cases can cause bizarre behavior <pytest-cov-666_>_.

• Refactor: some code unreachable code paths in parser.py were changed to

... (truncated)

Commits

• 6134266 docs: sample HTML for 7.6.8
• 041f963 docs: prep for 7.6.8
• 7fe48b6 build: don't search generated report files
• f219144 docs: start changelog entries with capital letters
• d1a916a fix: a line that branches nowhere must always raise an exception
• 2ace7a2 fix: don't assume 'no branches' means 'not executed' #1896
• 3ed5915 style: all of ci should use underscores
• 0db86f2 build: automate updating readthedocs
• 2a89551 chore: make upgrade (not sure why files became absolute)
• ba9c157 chore: make doc_upgrade
• 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)