coverage (dependency) 7.15.4 -> 7.16.0

Risk: 🟢 Safe

The Deep Dive

Update Scope

This single-file lock refresh updates only coverage.py from 7.15.4 to 7.16.0. pytest-cov and every other locked package are unchanged, and coverage is a development-only transitive dependency used by the repository's pytest coverage hook.

Features & UX

• Cross-platform data combining: 7.16.0 automatically normalizes path separators when combining coverage data produced on different operating systems, reducing the need for [paths] mappings. This behavior is automatic, but this repository invokes one ordinary pytest --cov process, and its complete coverage configuration contains neither combining nor [paths], so it does not activate the changed path.
• Context API return value: Coverage.switch_context() now returns the previous context, an additive API capability requiring callers to use the Python API. The repository's coverage integration is declarative and limited to pytest-cov plus TOML settings, and repository code search finds no coverage API imports or dynamic-context configuration, so the PR leaves the existing test workflow unchanged.

Key Fixes

• Safer configuration diagnostics: 7.16.0 validates negative precision, invalid context regexes, and wrong-typed TOML values with explicit configuration errors instead of tracebacks or misleading SQLite errors. The repository configures source, fail_under, show_missing, and string-valued exclude_lines, and the successful lint/coverage check confirms 7.16.0 accepts them.
• Path alias and annotation correctness: Path aliases now replace only the matched leading prefix, and coverage annotate -d preserves non-.py extensions. The complete coverage configuration contains no aliases, and the hook requests only pytest's terminal coverage report, so neither fix changes its results.
• Earlier multiprocessing failure: coverage run now rejects branch options combined with a multiprocessing concurrency list before subprocess execution. The repository's complete run configuration sets only source = ["lib"], so the tightening is not applicable.

Hazards & Risks

None identified. Coverage.py 7.16.0 documents no breaking changes, migrations, removals, or deprecations; its Python >=3.10 floor remains compatible with this project's Python >=3.11 requirement. The only behavior tightening concerns multiprocessing plus branch coverage, neither of which appears in the repository's complete coverage configuration, and the relevant pytest/coverage lint check succeeded.

Sources

• Coverage.py 7.16.0 release notes
• Coverage.py 7.15.4 to 7.16.0 comparison
• Coverage.py 7.16.0 changelog
• Coverage.py 7.16.0 PyPI metadata
• Coverage.py security policy

🟢 Verdict: Safe

Safe: this development-only coverage update introduces no relevant compatibility, migration, security, or runtime concern for the repository's configured usage, and the actual lint/pytest coverage gate passed. The pending Renovate release-age check is a normal timing gate, not evidence of a defect in the update.

Actions Menu

1. Merge — wait for the pending release-age gate, then rebase-merge PR 36.
2. Review later — take no action and return to the Renovate queue later.
3. Close — close PR 36; Renovate will not recreate an ignored update unless it is unignored.