Bump coverage from 7.15.4 to 7.16.0

[dependabot]

Bumps coverage from 7.15.4 to 7.16.0.

Release notes

Sourced from coverage's releases.

7.16.0

Version 7.16.0 — 2026-08-28

• When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define [paths] configuration to combine data across operating systems. Fixes issue 2266.
• The Coverage.switch_context() method now returns the previous context.
• Fix: previously, a [paths] pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in pull 2268.
• Fixes to validation of options and configuration settings:
  • Negative precision settings now always cause useful error messages (pull 2261).
  • An invalid regex in the --contexts option (or the [report] contexts setting) reported a confusing “Couldn’t use data file …: user-defined function raised exception” error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (pull 2262).
  • Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren’t strings (like omit, exclude_lines, or a [paths] entry), file settings like data_file, and any wrong-typed value in the [paths] section (pull 2263).
  • coverage run refuses run-affecting command-line options like --branch alongside --concurrency=multiprocessing, since they can’t reach the subprocesses. The check only recognized multiprocessing as the entire option value, so --concurrency=multiprocessing,thread slipped through and failed later with “Can’t combine statement coverage data with branch data”. Each named concurrency library is now properly considered (pull 2270).
• Fix: coverage annotate -d DIR raised an AssertionError if any measured file had an extension other than .py, such as a .pyw file on Windows. The original extension is now restored on the annotated copy (pull 2265).

➡️  PyPI page: coverage 7.16.0. :arrow_right:  To install: python3 -m pip install coverage==7.16.0

Changelog

Sourced from coverage's changelog.

Version 7.16.0 — 2026-08-28

• When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define [paths] configuration to combine data across operating systems. Fixes issue 2266_.

• The :meth:.Coverage.switch_context method now returns the previous context.

• Fix: previously, a [paths] pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in pull 2268_.

• Fixes to validation of options and configuration settings:

  • Negative precision settings now always cause useful error messages (pull 2261_).

  • An invalid regex in the --contexts option (or the [report] contexts setting) reported a confusing "Couldn't use data file ...: user-defined function raised exception" error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (pull 2262_).

  • Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren't strings (like omit, exclude_lines, or a [paths] entry), file settings like data_file, and any wrong-typed value in the [paths] section (pull 2263_).

  • coverage run refuses run-affecting command-line options like --branch alongside --concurrency=multiprocessing, since they can't reach the subprocesses. The check only recognized multiprocessing as the entire option value, so --concurrency=multiprocessing,thread slipped through and failed later with "Can't combine statement coverage data with branch data". Each named concurrency library is now properly considered (pull 2270_).

• Fix: coverage annotate -d DIR raised an AssertionError if any measured file had an extension other than .py, such as a .pyw file on Windows. The original extension is now restored on the annotated copy (pull 2265_).

.. _pull 2261: coveragepy/coveragepy#2261 .. _pull 2262: coveragepy/coveragepy#2262 .. _pull 2263: coveragepy/coveragepy#2263 .. _pull 2265: coveragepy/coveragepy#2265 .. _issue 2266: coveragepy/coveragepy#2266 .. _pull 2268: coveragepy/coveragepy#2268

... (truncated)

Commits

• 3e9fc16 docs: prep for 7.16.0
• 38be8d1 build: control check-manifest explicitly
• 8eb1266 docs(build): no longer commit sample_html
• 1a8b3fa docs: remove sample_html
• aeaa79b docs: linklint is now sphinx-linklint
• d5eaf3f test: a branchless way to re-add extensions
• 57e52fd docs: adjust CHANGES for #2270
• b9d304d fix: check for multiprocessing in a --concurrency list (#2270)
• a6ef928 chore: make upgrade
• 070461f chore: bump the action-dependencies group with 4 updates (#2271)
• Additional commits viewable in compare view

[github-actions]

🤖 Claude Code Review

Code Review: Bump coverage 7.15.4 → 7.16.0

This is a routine Dependabot dependency bump touching two lines in pyproject.toml (lines 38 and 87), both updated consistently for the python_version > '3.11' coverage pin in the development and test extras.

Code Quality

• ✅ Follows existing style conventions (consistent with surrounding pinned-version syntax)
• ✅ No commented-out code
• ✅ N/A — no variables/functions introduced
• ✅ DRY — both occurrences of the pin were updated together, no duplication introduced
• ✅ No defects — verified both coverage==7.15.4 references in pyproject.toml were changed to 7.16.0 (lines 38, 87); no stray/missed occurrence
• ✅ No CLAUDE.md changes in this PR

Testing

• N/A — dependency version bump only, no new functions/endpoints/logic

Documentation

• ✅ CHANGELOG.md not updated, but consistent with repo precedent — prior dependency-bump commits (e.g., isort, build bumps in recent history) also did not touch CHANGELOG.md
• N/A — no README/API doc changes needed

Security

• ✅ No hardcoded credentials
• ✅ No .lic files or AQAAAD-prefixed strings found in the diff or repo
• N/A — no input validation/error handling/logging changes

Overall: ✅ Approve. Low-risk, mechanical version bump with both pin locations updated consistently.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

PR Code Review

Scope: Dependabot-style dependency bump — coverage 7.15.4 → 7.16.0 (Python > 3.11 pin) in two pyproject.toml dependency groups (development, test). Consistent with the pattern of recent merged commits (isort, virtualenv, build bumps) in this repo's history.

Code Quality

• ✅ Style conventions — Change matches existing TOML formatting/quoting conventions in pyproject.toml.
• ✅ No commented-out code — N/A, none present.
• ✅ Meaningful variable names — N/A, no code.
• ✅ DRY — The coverage version is duplicated across pyproject.toml:38 (development group) and pyproject.toml:87 (test group), and both were updated consistently. This duplication predates the PR and matches the same pattern already used for pytest in both groups, so not a new issue introduced here.
• ✅ Defects — Straightforward version bump, no logic to break. No syntax issues in the diff.
• ✅ CLAUDE.md review — No changes to .claude/CLAUDE.md in this diff; existing file remains general-purpose (commands, architecture) and contains nothing environment-specific to a single developer's machine.

Testing

• ⚠️ Not verifiable in this environment — No network access to confirm coverage==7.16.0 installs cleanly or that the test/lint suite passes against it. Recommend confirming CI is green on this PR before merge (standard for dependency bumps).
• ✅ No new functions/endpoints, so unit/integration test requirements don't apply.

Documentation

• ✅ CHANGELOG.md — Not updated, but this is consistent with prior dependency-bump commits in this repo (e.g. d3f7bb9, 29fe280, c70cec6 — none of which touched CHANGELOG.md either). Not flagging as a defect since it matches established project convention for automated bumps.
• ✅ No README/API doc changes needed for a dependency version bump.

Security

• ✅ No hardcoded credentials.
• ✅ No .lic files or AQAAAD-prefixed license strings in this diff.
• ✅ No sensitive data in the diff.
• N/A input validation / error handling — no code changes.

Summary

No issues found. This is a low-risk, mechanical dependency bump consistent with the repo's existing automated-update pattern. Safe to merge pending green CI.

Automated code review analyzing defects and coding standards