chore(deps): update dependency coverage to v6.5.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	6.3.3 → 6.5.0

---

Release Notes

coveragepy/coveragepy (coverage)

v6.5.0

Compare Source

• The JSON report now includes details of which branches were taken, and which
  are missing for each file. Thanks, Christoph Blessing <pull 1438_>. Closes
  issue 1425.

• Starting with coverage.py 6.2, class statements were marked as a branch.
  This wasn't right, and has been reverted, fixing issue 1449_. Note this
  will very slightly reduce your coverage total if you are measuring branch
  coverage.

• Packaging is now compliant with PEP 517, closing issue 1395.

• A new debug option --debug=pathmap shows details of the remapping of
  paths that happens during combine due to the [paths] setting.

• Fix an internal problem with caching of invalid Python parsing. Found by
  OSS-Fuzz, fixing their bug 50381_.

.. _bug 50381: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50381
.. _PEP 517: https://peps.python.org/pep-0517/
.. _issue 1395: #​1395
.. _issue 1425: #​1425
.. _issue 1449: #​1449
.. _pull 1438: #​1438

.. _changes_6-4-4:

v6.4.4

Compare Source

• Wheels are now provided for Python 3.11.

.. _changes_6-4-3:

v6.4.3

Compare Source

• Fix a failure when combining data files if the file names contained glob-like
  patterns. Thanks, Michael Krebs and Benjamin Schubert <pull 1405_>_.

• Fix a messaging failure when combining Windows data files on a different
  drive than the current directory, closing issue 1428. Thanks, Lorenzo Micò <pull 1430_>.

• Fix path calculations when running in the root directory, as you might do in
  a Docker container. Thanks Arthur Rio <pull 1403_>_.

• Filtering in the HTML report wouldn't work when reloading the index page.
  This is now fixed. Thanks, Marc Legendre <pull 1413_>_.

• Fix a problem with Cython code measurement, closing issue 972. Thanks,
  Matus Valo <pull 1347_>.

.. _issue 972: #​972
.. _issue 1428: #​1428
.. _pull 1347: #​1347
.. _pull 1403: #​1403
.. _pull 1405: #​1405
.. _pull 1413: #​1413
.. _pull 1430: #​1430

.. _changes_6-4-2:

v6.4.2

Compare Source

• Updated for a small change in Python 3.11.0 beta 4: modules now start with a
  line with line number 0, which is ignored. This line cannot be executed, so
  coverage totals were thrown off. This line is now ignored by coverage.py,
  but this also means that truly empty modules (like __init__.py) have no
  lines in them, rather than one phantom line. Fixes issue 1419_.

• Internal debugging data added to sys.modules is now an actual module, to
  avoid confusing code that examines everything in sys.modules. Thanks,
  Yilei Yang <pull 1399_>_.

.. _issue 1419: #​1419
.. _pull 1399: #​1399

.. _changes_6-4-1:

v6.4.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: #​1420
.. _issue 2064: #​2064
.. _issue 2070: #​2070

.. _changes_7-11-0:

v6.4

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: #​1420
.. _issue 2064: #​2064
.. _issue 2070: #​2070

.. _changes_7-11-0:

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.