Bump coverage from 7.10.7 to 7.13.1

[dependabot]

Bumps coverage from 7.10.7 to 7.13.1.

Changelog

Sourced from coverage's changelog.

Version 7.13.1 — 2025-12-28

• Added: the JSON report now includes a "start_line" key for function and class regions, indicating the first line of the region in the source. Closes issue 2110_.

• Added: The debug data command now takes file names as arguments on the command line, so you can inspect specific data files without needing to set the COVERAGE_FILE environment variable.

• Fix: the JSON report used to report module docstrings as executed lines, which no other report did, as described in issue 2105_. This is now fixed, thanks to Jianrong Zhao.

• Fix: coverage.py uses a more disciplined approach to detecting where third-party code is installed, and avoids measuring it. This shouldn't change any behavior. If you find that it does, please get in touch.

• Performance: data files that will be combined now record their hash as part of the file name. This lets us skip duplicate data more quickly, speeding the combining step.

• Docs: added a section explaining more about what is considered a missing branch and how it is reported: :ref:branch_explain, as requested in issue 1597. Thanks to Ayisha Mohammed <pull 2092_>.

• Tests: the test suite misunderstood what core was being tested if COVERAGE_CORE wasn't set on 3.14+. This is now fixed, closing issue 2109_.

.. _issue 1597: coveragepy/coveragepy#1597 .. _pull 2092: coveragepy/coveragepy#2092 .. _issue 2105: coveragepy/coveragepy#2105 .. _issue 2109: coveragepy/coveragepy#2109 .. _issue 2110: coveragepy/coveragepy#2110

.. _changes_7-13-0:

Version 7.13.0 — 2025-12-08

• Feature: coverage.py now supports :file:.coveragerc.toml configuration files. These files use TOML syntax and take priority over :file:pyproject.toml but lower priority than :file:.coveragerc files. Closes issue 1643_ thanks to Olena Yefymenko <pull 1952_>_.

• Fix: we now include a permanent .pth file which is installed with the code, fixing issue 2084_. In 7.12.1b1 this was done incorrectly: it didn't work when using the source wheel (py3-none-any). This is now fixed. Thanks,

... (truncated)

Commits

• a6afdc3 docs: sample HTML for 7.13.1
• a497081 docs: prep for 7.13.1
• e992033 docs: polish up CHANGES
• 18bba6e chore: bump the action-dependencies group with 4 updates (#2111)
• 80fb808 refactor: (?x:...) lets us use re.VERBOSE even when combining later
• cc272bd docs: leave a comment so we'll find this when 3.12 is the minimum
• 70d007d types: be explicit
• a2c1940 types: fully import modules that will be patched
• 57b975d types: explicit Protocol inheritance permits changing parameter names
• 63ec12d types: clarify that morfs arguments can be a single morf
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🤖 Claude Code Review

Code Review Results

Summary

This is a dependency version bump for the coverage package from version 7.10.7 to 7.13.1. The change is consistent and appears across both development and test dependency groups.

---

Code Quality

✅ Code follows style guide

• Status: ✅ PASS
• Details: This is a dependency version update in pyproject.toml. The formatting is consistent with Python packaging standards. No code style issues detected.

✅ No commented-out code

• Status: ✅ PASS
• Details: No commented-out code present in the diff.

✅ Meaningful variable names

• Status: ✅ PASS (N/A)
• Details: Not applicable - this is a dependency version update, no variables involved.

✅ DRY principle followed

• Status: ✅ PASS
• Details: The version is updated in both places where coverage is specified (lines 36 and 56 in pyproject.toml), maintaining consistency.

✅ Identify Defects

• Status: ✅ PASS
• Details: No bugs, logic errors, or security vulnerabilities detected. This is a straightforward dependency version bump.

✅ Project memory claude configuration

• Status: ✅ PASS (N/A)
• Details: No .claude/CLAUDE.md file exists in this project, so no project-specific requirements to consider.

---

Testing

❌ Unit tests for new functions

• Status: ❌ NEEDS ATTENTION
• Details: While no new functionality was added, it's recommended to run the existing test suite with the new coverage version to ensure compatibility. No evidence of test execution results in the PR.

❌ Integration tests for new endpoints

• Status: ✅ PASS (N/A)
• Details: Not applicable - no new endpoints added.

❌ Edge cases covered

• Status: ✅ PASS (N/A)
• Details: Not applicable for dependency updates.

⚠️ Test coverage > 80%

• Status: ⚠️ NEEDS VERIFICATION
• Details: Cannot verify current test coverage from the diff alone. The version bump itself doesn't affect coverage, but it should be verified that the new version of coverage tool works correctly.

---

Documentation

❌ Readme updated if needed

• Status: ✅ PASS (N/A)
• Details: README.md does not require updates for internal dependency version changes.

✅ API docs updated

• Status: ✅ PASS (N/A)
• Details: No API changes - not applicable.

✅ Inline comments for complex logic

• Status: ✅ PASS (N/A)
• Details: Not applicable for dependency updates.

❌ CHANGELOG.md updated

• Status: ❌ FAIL
• Details: CHANGELOG.md at /home/runner/work/code-snippets-v4/code-snippets-v4/CHANGELOG.md has not been updated to reflect this dependency change. While this is a minor dependency bump, it should be documented per the project's changelog policy.

✅ Markdown files follow CommonMark

• Status: ✅ PASS (N/A)
• Details: No markdown files were modified in this PR.

---

Security

✅ No hardcoded credentials

• Status: ✅ PASS
• Details: No credentials present in the diff.

✅ Input validation implemented

• Status: ✅ PASS (N/A)
• Details: Not applicable for dependency updates.

✅ Proper error handling

• Status: ✅ PASS (N/A)
• Details: Not applicable for dependency updates.

✅ No sensitive data in logs

• Status: ✅ PASS
• Details: No logging code present in the diff.

✅ No license files checked in

• Status: ✅ PASS
• Details: No .lic files or AQAAAD strings detected in the diff.

---

Overall Assessment

Recommendation: ✅ APPROVE with minor suggestions

Critical Issues

• None

Important Issues

1. CHANGELOG.md not updated (pyproject.toml:36, 56) - Add an entry documenting the coverage version bump from 7.10.7 to 7.13.1

Suggestions

1. Verify that the test suite passes with the new coverage version
2. Consider if this version bump fixes any known issues or adds features that should be noted

Positive Notes

• Clean, focused change
• Consistent update across both dependency groups
• Follows semantic versioning for dependency specifications

---

Automated code review analyzing defects and coding standards