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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	==7.14.2 → ==7.14.3

---

Release Notes

coveragepy/coveragepy (coverage)

v7.14.3

Compare Source

• Fix: the default ... exclusion rule now also matches function bodies
  whose closing return-type bracket is on its own line (for example, after a
  long -> dict[ ... ] annotation that a formatter has split over multiple
  lines). Closes issue 2185, thanks Mengjia Shang <pull 2196_>.

• Fix: On 3.13t, we incorrectly issued Couldn't import C tracer errors.
  We can't import the C tracer because in 7.14.2 we stopped shipping compiled
  wheels for 3.13t. Thanks, Hugo van Kemenade <pull 2203_>_.

.. _issue 2185: #​2185
.. _pull 2196: #​2196
.. _pull 2203: #​2203

.. _changes_7-14-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 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 was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

• Chores
  • Updated development dependencies to latest compatible versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

The coverage package in the dev optional dependency group of pyproject.toml is bumped from version 7.14.2 to 7.14.3. No other files or configuration settings are modified.

Changes

Dependency Version Bump

Layer / File(s)	Summary
coverage 7.14.2 → 7.14.3 pyproject.toml	The pinned coverage version in the dev optional dependencies is updated from 7.14.2 to 7.14.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the coverage dependency from 7.14.2 to 7.14.3, which is the sole modification in this PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/coverage-7.x

---

_{Comment @coderabbitai help to get the list of available commands.}

[agents-workflows-bot]

Workflow source needed

PR #36 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

[github-actions]

🤖 Keepalive Loop Status

PR #36 | Agent: Codex | Iteration 0/5

Current State

Metric	Value
Iteration progress	[----------] 0/5
Action	wait (missing-agent-label)
Disposition	skipped (transient)
Gate	failure
Tasks	0/2 complete
Timeout	45 min (default)
Timeout usage	1m elapsed (3%, 44m remaining)
Keepalive	❌ disabled
Autofix	❌ disabled

🔍 Failure Classification

| Error type | infrastructure |
| Error category | resource |
| Suggested recovery | Confirm the referenced resource exists (repo, PR, branch, workflow, or file). |

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pyproject.toml`:
- Line 20: The coverage dependency in pyproject.toml has been updated to 7.14.3,
but requirements.lock still pins the old version 7.14.2, which breaks
reproducible builds and CI consistency. Regenerate the requirements.lock file
using your project's lock file generation tool (typically pip-compile, uv lock,
poetry lock, or similar depending on your setup) to synchronize it with the
updated coverage==7.14.3 dependency specified in pyproject.toml.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b3f9cc77-f943-45b5-a632-980e38377887

📥 Commits

Reviewing files that changed from the base of the PR and between 1fea9ac and 7d17843.

📒 Files selected for processing (1)

• pyproject.toml

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• stranske/Workflows (auto-detected)

📜 Review details

⏰ Context from checks skipped due to timeout. (2)

• GitHub Check: Python CI / python 3.12
• GitHub Check: autofix / autofix

🧰 Additional context used

📓 Path-based instructions (3)

pyproject.toml

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

pyproject.toml: For mypy type errors on modules with existing type issues, add overrides to pyproject.toml with ignore_errors = true instead of using exclude patterns
Use ignore_errors = true in mypy overrides instead of exclude patterns because exclude only prevents direct checking, not imports from other modules

Files:

• pyproject.toml

{pyproject.toml,.github/workflows/**/*.{yml,yaml}}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Ensure coverage threshold settings match between pyproject.toml ([tool.coverage.report] fail_under) and workflow files (coverage-min setting)

Files:

• pyproject.toml

{requirements*.txt,setup.py,pyproject.toml}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Pin jsonschema to compatible range jsonschema>=4.17.3,<4.23.0 due to breaking changes in version 4.23.0+ with referencing

Files:

• pyproject.toml

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Regenerate requirements.lock to match the updated coverage dependency.

The pyproject.toml update to coverage==7.14.3 creates a contract mismatch with requirements.lock, which still pins coverage==7.14.2 (as shown in the relevant context). Lock files are consumed by CI tooling and developers for reproducible installs; stale locks defeat that guarantee.

Regenerate the lock file to synchronize with this dependency update.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@pyproject.toml` at line 20, The coverage dependency in pyproject.toml has
been updated to 7.14.3, but requirements.lock still pins the old version 7.14.2,
which breaks reproducible builds and CI consistency. Regenerate the
requirements.lock file using your project's lock file generation tool (typically
pip-compile, uv lock, poetry lock, or similar depending on your setup) to
synchronize it with the updated coverage==7.14.3 dependency specified in
pyproject.toml.

[stranske]

Closing as superseded by stranske/Workflows#2507. Coverage is a Workflows-owned shared autofix/dev-tool pin, so the canonical env file, pyproject.toml, templates, and requirements.lock need to move together before the integration repo is synced. This pyproject-only Renovate PR would leave the lockfile and shared pin set inconsistent.