[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	7.17.2 → 7.17.3

---

Release Notes

coveragepy/coveragepy (coverage)

v7.17.3

Compare Source

• Fix: using patch = fork, a child process wasn't measured unless patch = subprocess was also used, as described in issue 2340. This is now fixed
  in pull 2342.

• Fix: the JSON report keys functions and classes by name, but names can
  repeat, for example a property getter and setter. Only the last one was
  kept, so the others were missing from the report. Now repeated names get a
  @<line number> suffix, as in the LCOV report. pull 2353_.

• Fix: when combining parallel data files, a file that disappears after it
  has been listed (for example, when the process writing it is still finishing
  its write) is now reported with a warning, instead of stopping the combine
  with a DataError. This was a regression in 7.17.1. Closes issue 2364_.

• Fix: with patch = subprocess on Python 3.13, a measured subprocess that
  was stopped with SIGINT would exit with status 1 instead of dying from the
  signal. This was a regression in 7.17.1, and is now fixed, closing issue 2362_.

• Performance: on Python 3.13 and later, using the C tracer should result in
  test suites running about 8% to 12% faster (pull 2371_).

.. _issue 2340: #​2340
.. _pull 2342: #​2342
.. _pull 2353: #​2353
.. _issue 2364: #​2364
.. _issue 2362: #​2362
.. _pull 2371: #​2371

.. _changes_7-17-2:

---

Configuration

📅 Schedule: (UTC)

• 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 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.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage · +0.00% coverage variation

Metric	Results
Coverage variation	✅ +0.00% coverage variation
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (189ed33)	559	559	100.00%
Head commit (d68330d)	559 (+0)	559 (+0)	100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#874)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (189ed33) to head (d68330d).

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #874   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          559       559           
  Branches        41        41           
=========================================
  Hits           559       559           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.