fix(deps): update dependency coverage to v7.14.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	==7.13.5 → ==7.14.0

---

Release Notes

coveragepy/coveragepy (coverage)

v7.14.0

Compare Source

• Feature: now when running one of the reporting commands, if there are
  parallel data files that need combining, they will be implicitly combined
  before creating the report. There is no option to avoid the combination; let
  us know if you have a use case that requires it. Thanks, Tim Hatch <pull 2162_>. Closes issue 1781.

• Fix: the output from combine was too verbose, listing each file
  considered. Now it shows a single line with the counts of files combined,
  files skipped, and files with errors. The -q flag suppresses this line.
  The old detailed lines are available with the new --debug=combine option.

• Fix: running a Python file through a symlink now sets the sys.path correctly,
  matching regular Python behavior. Fixes issue 2157_.

• Fix: Collector.flush_data could fail with "RuntimeError: Set changed
  size during iteration" when a tracer in another thread added a line to the
  per-file set that add_lines (or add_arcs) was iterating. The values
  passed to CoverageData are now snapshotted via dict.copy() and
  set.copy(), which are atomic under the GIL. Thanks, Alex Vandiver <pull 2165_>_.

• Fix: the soft keyword lazy is now bolded in HTML reports.

• We are no longer testing eventlet support. Eventlet started issuing stern
  deprecation warnings that break our tests. Our support code is still there.

.. _issue 1781: #​1781
.. _issue 2157: #​2157
.. _pull 2162: #​2162
.. _pull 2165: #​2165

.. _changes_7-13-5:

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

• Branch creation
  • "before 5am on Monday"
• 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 these updates again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: AIMER-ROOT/uv.lock

Command failed: uv lock --upgrade-package coverage
Using CPython 3.14.5 interpreter at: /opt/containerbase/tools/python/3.14.5/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ sys_platform == 'darwin'):
  ╰─▶ Because litellm==1.83.3 depends on python-dotenv==1.0.1 and
      openrag==0.4.1 depends on litellm==1.83.3, we can conclude that
      openrag==0.4.1 depends on python-dotenv==1.0.1.
      And because only the following versions of openrag are available:
          openrag<=0.4.1
          openrag>0.5.0
      and aimer depends on openrag>=0.4.1, we can conclude that aimer depends
      on python-dotenv==1.0.1.
      And because aimer depends on python-dotenv==1.2.2 and your workspace
      requires aimer, we can conclude that your workspace's requirements are
      unsatisfiable.

      hint: The resolution failed for an environment that is not the current
      one, consider limiting the environments with `tool.uv.environments`.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{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.}