Skip to content

chore(deps): update dependency coverage to >=7.16,<7.17 - #680

Merged
jooola merged 1 commit into
mainfrom
renovate/coverage-7.x
Sep 3, 2026
Merged

chore(deps): update dependency coverage to >=7.16,<7.17#680
jooola merged 1 commit into
mainfrom
renovate/coverage-7.x

Conversation

@renovate

@renovate renovate Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
coverage >=7.15,<7.16>=7.16,<7.17 age confidence

Release Notes

coveragepy/coveragepy (coverage)

v7.16.0

Compare Source

  • 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: #​2261
.. _pull 2262: #​2262
.. _pull 2263: #​2263
.. _pull 2265: #​2265
.. _issue 2266: #​2266
.. _pull 2268: #​2268
.. _pull 2270: #​2270

.. _changes_7-15-4:


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.

@renovate renovate Bot changed the title chore(deps): update dependency coverage to >=7.16,<7.17 chore(deps): update dependency coverage to >=7.16,<7.17 - autoclosed Sep 3, 2026
@renovate renovate Bot closed this Sep 3, 2026
@renovate
renovate Bot deleted the renovate/coverage-7.x branch September 3, 2026 05:13
@renovate renovate Bot changed the title chore(deps): update dependency coverage to >=7.16,<7.17 - autoclosed chore(deps): update dependency coverage to >=7.16,<7.17 Sep 3, 2026
@renovate renovate Bot reopened this Sep 3, 2026
@renovate
renovate Bot force-pushed the renovate/coverage-7.x branch from c43a147 to f048fc5 Compare September 3, 2026 08:35
@jooola
jooola merged commit 85b401c into main Sep 3, 2026
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant