Bump coverage[toml] from 7.3.1 to 7.6.11 in /tools/deps

[dependabot]

Bumps coverage[toml] from 7.3.1 to 7.6.11.

Release notes

Sourced from coverage[toml]'s releases.

7.6.11

Version 7.6.11 — 2025-02-08

• Fix: a memory leak in CTracer has been fixed. The details are in issue 1924 and pytest-dev 676. This should reduce the memory footprint for everyone even if it hadn’t caused a problem before.
• We now ship a py3-none-any.whl wheel file. Thanks, Russell Keith-Magee.

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

7.6.10

Version 7.6.10 — 2024-12-26

• Fix: some descriptions of missing branches in HTML and LCOV reports were incorrect when multi-line statements were involved (issue 1874 and issue 1875). These are now fixed.
• Fix: Python 3.14 defers evaluation of annotations by moving them into separate code objects. That code is rarely executed, so coverage.py would mark them as missing, as reported in issue 1908. Now they are ignored by coverage automatically.
• Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving mocks, imports, and trace functions: issue 1902. To be honest, I don’t understand the problem or the solution, but git bisect helped find it, and now it’s fixed.
• Docs: re-wrote the Measuring subprocesses page to put multiprocessing first and to highlight the correct use of https://docs.python.org/3/library/multiprocessing.html#multiprocessing.pool.Pool.

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

7.6.9

Version 7.6.9 — 2024-12-06

• Fix: Tomas Uribe fixed a performance problem in the XML report. Large code bases should produce XML reports much faster now.

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

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.

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

Version 7.6.11 — 2025-02-08

• Fix: a memory leak in CTracer has been fixed. The details are in issue 1924_ and pytest-dev 676_. This should reduce the memory footprint for everyone even if it hadn't caused a problem before.

• We now ship a py3-none-any.whl wheel file. Thanks, Russell Keith-Magee <pull 1914_>_.

.. _pull 1914: nedbat/coveragepy#1914 .. _issue 1924: nedbat/coveragepy#1924 .. _pytest-dev 676: pytest-dev/pytest-cov#676

.. _changes_7-6-10:

Version 7.6.10 — 2024-12-26

• Fix: some descriptions of missing branches in HTML and LCOV reports were incorrect when multi-line statements were involved (issue 1874_ and issue 1875_). These are now fixed.

• Fix: Python 3.14 defers evaluation of annotations <pep649_>_ by moving them into separate code objects. That code is rarely executed, so coverage.py would mark them as missing, as reported in issue 1908_. Now they are ignored by coverage automatically.

• Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving mocks, imports, and trace functions: issue 1902_. To be honest, I don't understand the problem or the solution, but git bisect helped find it, and now it's fixed.

• Docs: re-wrote the :ref:subprocess page to put multiprocessing first and to highlight the correct use of :class:multiprocessing.Pool <python:multiprocessing.pool.Pool>.

.. _issue 1874: nedbat/coveragepy#1874 .. _issue 1875: nedbat/coveragepy#1875 .. _issue 1902: nedbat/coveragepy#1902 .. _issue 1908: nedbat/coveragepy#1908 .. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#pep-649-deferred-evaluation-of-annotations

.. _changes_7-6-9:

Version 7.6.9 — 2024-12-06

• Fix: Tomas Uribe fixed <pull 1901_>_ a performance problem in the XML

... (truncated)

Commits

• a20898d docs: sample HTML for 7.6.11
• 938d519 docs: prep for 7.6.11
• 27ee4ff test: free-threading builds were failing the old leak test #1924
• f473b87 test: it could be useful to disable branch coverage in this helper
• f85d9b7 fix: prevent code objects from leaking #1924
• ae8d3b9 chore: make upgrade
• 156981f build: zizmor can't tell this is safe
• 6603021 chore: bump the action-dependencies group with 6 updates (#1922)
• d6a1e5b test: run the pytracer first so .tox is left with a c extension for ad-hoc use
• cd2db93 docs: a reminder about when RESUME applies
• 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)

Summary by Sourcery

Build:

• Upgrade coverage[toml] in the test requirements.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the coverage[toml] dependency from version 7.3.1 to 7.6.11 by modifying the requirements-tests.txt file. The upgrade includes various bug fixes and improvements as outlined in the release notes, such as fixes for memory leaks, performance improvements, and better reporting.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Bumped the coverage[toml] dependency to a newer version	Updated the dependency version from 7.3.1 to 7.6.11 in the requirements file Reflected the latest bug fixes and enhancements from upstream release notes	tools/deps/requirements-tests.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[dependabot]

Superseded by #5586.