chore(deps): update dependency coverage to v7.12.0

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
coverage	dev	minor	7.10.7 -> 7.12.0

---

Release Notes

coveragepy/coveragepy (coverage)

v7.12.0

Compare Source

• The HTML report now shows separate coverage totals for statements and
  branches, as well as the usual combined coverage percentage. Thanks to Ryuta
  Otsuka for the discussion <issue 2081_>_ and the implementation <pull 2085_>_.

• The JSON report now includes separate coverage totals for statements and
  branches, thanks to Ryuta Otsuka <pull 2090_>_.

• Fix: except* clauses were not handled properly under the "sysmon"
  measurement core, causing KeyError exceptions as described in issue 2086_.
  This is now fixed.

• Fix: we now defend against aggressive mocking of open() that could cause
  errors inside coverage.py. An example of a failure is in issue 2083_.

• Fix: in unusual cases where a test suite intentionally exhausts the system's
  file descriptors to test handling errors in open(), coverage.py would
  fail when trying to open source files, as described in issue 2091_. This
  is now fixed.

• A small tweak to the HTML report: file paths now use thin spaces around
  slashes to make them easier to read.

.. _issue 2081:https://github.com/coveragepy/coveragepy/issues/20811
.. _issue 2083https://github.com/coveragepy/coveragepy/issues/208383
.. _pull 208https://github.com/coveragepy/coveragepy/pull/2085085
.. _issue 20https://github.com/coveragepy/coveragepy/issues/20862086
.. _pull 2https://github.com/coveragepy/coveragepy/pull/2090/2090
.. _issue https://github.com/coveragepy/coveragepy/issues/2091s/2091

.. _changes_7-11-3:

v7.11.3

Compare Source

• Fix: the 7.11.1 changes meant that conflicts between a requested measurement
  core and other settings would raise an error. This was a breaking change from
  previous behavior, as reported in issue 2076_ and issue 2078_.

  The previous behavior has been restored: when the requested core conflicts
  with other settings, another core is used instead, and a warning is issued.

• For contributors: the repo has moved from Ned's nedbat GitHub account_ to
  the coveragepy GitHub organization_. The default branch has changed from
  master to main.

.. _issue 2076:https://github.com/coveragepy/coveragepy/issues/20766
.. _issue 2078https://github.com/coveragepy/coveragepy/issues/207878
.. _nedbat GitHub account: https://github.com/nedbat
.. _coveragepy GitHub organization: https://github.com/coveragepy

.. _changes_7-11-2:

v7.11.2

Compare Source

• Fix: using the "sysmon" measurement core in 7.11.1, if Python code was
  claimed to come from a non-Python file, a NotPython exception could be
  raised. This could happen for example with Jinja templates compiled to
  Python, as reported in issue 2077_. This is now fixed.

• Doc: corrected the first entry in the 7.11.1 changelog.

.. _issue 2077:https://github.com/coveragepy/coveragepy/issues/20777

.. _changes_7-11-1:

v7.11.1

Compare Source

• Fix: some chanages to details of how the measurement core is chosen, and how
  conflicting settings are handled. The "sysmon" core cannot be used with some
  conurrency settings, with dynamic context, and in Python 3.12/3.13, with
  branch measurement.

  • If the core is not specified and defaults to "sysmon" (Python 3.14+), but
    other settings conflict with sysmon, then the "ctrace" core will be used
    instead with no warning. For concurrency conflicts, this used to produce an
    error, as described in issue 2064_.

  • If the "sysmon" core is explicitly requested in your configuration, but
    other settings conflict, an error is now raised. This used to produce a
    warning.

• Fix: some multi-line case clauses or for loops (and probably other
  constructs) could cause incorrect claims of missing branches with the
  sys.monitoring core, as described in issue 2070_. This is now fixed.

• Fix: when running in pytest under coverage, a breakpoint() would stop in
  the wrong frame, one level down from where it should, as described in issue 1420_. This was due to a coverage change in v6.4.1 that seemed to give a
  slight performance improvement, but I couldn't reproduce the performance
  gain, so it's been reverted, fixing the debugger problem.

• A new debug option --debug=core shows which core is in use and why.

• Split sqlite debugging information out of the sys :ref:coverage debug <cmd_debug> and :ref:cmd_run_debug options since it's bulky and not
  very useful.

• Updated the :ref:howitworks page to better describe the three different
  measurement cores.

.. _issue 1420:https://github.com/coveragepy/coveragepy/issues/14200
.. _issue 2064https://github.com/coveragepy/coveragepy/issues/206464
.. _issue 207https://github.com/coveragepy/coveragepy/issues/2070070

.. _changes_7-11-0:

v7.11.0

Compare Source

• Dropped support for Python 3.9, declared support for Python 3.15 alpha.

.. _changes_7-10-7:

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.