Bump coverage[toml] from 6.5.0 to 7.0.0

[dependabot]

Bumps coverage[toml] from 6.5.0 to 7.0.0.

Release notes

Sourced from coverage[toml]'s releases.

7.0.0

Nothing new beyond 7.0.0b1.

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

7.0.0b1

A number of changes have been made to file path handling, including pattern matching and path remapping with the [paths] setting (see [paths]). These changes might affect you, and require you to update your settings.

(This release includes the changes from 6.6.0b1

, since 6.6.0 was never released.)

• Changes to file pattern matching, which might require updating your configuration:
  • Previously, * would incorrectly match directory separators, making precise matching difficult. This is now fixed, closing issue 1407.
  • Now ** matches any number of nested directories, including none.
• Improvements to combining data files when using the [run] relative_files setting, which might require updating your configuration:
  • During coverage combine, relative file paths are implicitly combined without needing a [paths] configuration setting. This also fixed issue 991.
  • A [paths] setting like */foo will now match foo/bar.py so that relative file paths can be combined more easily.
  • The [run] relative_files setting is properly interpreted in more places, fixing issue 1280.
• When remapping file paths with [paths], a path will be remapped only if the resulting path exists. The documentation has long said the prefix had to exist, but it was never enforced. This fixes issue 608, improves issue 649, and closes issue 757.
• Reporting operations now implicitly use the [paths] setting to remap file paths within a single data file. Combining multiple files still requires the coverage combine step, but this simplifies some single-file situations. Closes issue 1212 and issue 713.
• The coverage report command now has a --format= option. The original style is now --format=text, and is the default.
  • Using --format=markdown will write the table in Markdown format, thanks to Steve Oswald, closing issue 1418.
  • Using --format=total will write a single total number to the output. This can be useful for making badges or writing status updates.
• Combining data files with coverage combine now hashes the data files to skip files that add no new information. This can reduce the time needed. Many details affect the speed-up, but for coverage.py’s own test suite, combining is about 40% faster. Closes issue 1483.
• When searching for completely un-executed files, coverage.py uses the presence of __init__.py files to determine which directories have source that could have been imported. However, implicit namespace packages don’t require __init__.py. A new setting [report] include_namespace_packages tells coverage.py to consider these directories during reporting. Thanks to Felix Horvat for the contribution. Closes issue 1383 and issue 1024.
• Fixed environment variable expansion in pyproject.toml files. It was overly broad, causing errors outside of coverage.py settings, as described in issue 1481 and issue 1345. This is now fixed, but in rare cases will require changing your pyproject.toml to quote non-string values that use environment substitution.
• An empty file has a coverage total of 100%, but used to fail with --fail-under. This has been fixed, closing issue 1470.
• The text report table no longer writes out two separator lines if there are no files listed in the table. One is plenty.
• Fixed a mis-measurement of a strange use of wildcard alternatives in match/case statements, closing issue 1421.
• Fixed internal logic that prevented coverage.py from running on implementations other than CPython or PyPy (issue 1474).
• The deprecated [run] note setting has been completely removed.

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

6.6.0b1

(Note: 6.6.0 final was never released. These changes are part of 7.0.0b1

.)

• Changes to file pattern matching, which might require updating your configuration:
  • Previously, * would incorrectly match directory separators, making precise matching difficult. This is now fixed, closing issue 1407.
  • Now ** matches any number of nested directories, including none.
• Improvements to combining data files when using the [run] relative_files setting:
  • During coverage combine, relative file paths are implicitly combined without needing a [paths] configuration setting. This also fixed issue 991.
  • A [paths] setting like */foo will now match foo/bar.py so that relative file paths can be combined more easily.
  • The setting is properly interpreted in more places, fixing issue 1280.
• Fixed environment variable expansion in pyproject.toml files. It was overly broad, causing errors outside of coverage.py settings, as described in issue 1481 and issue 1345. This is now fixed, but in rare cases will require changing your pyproject.toml to quote non-string values that use environment substitution.

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

Version 7.0.0 — 2022-12-18

Nothing new beyond 7.0.0b1.

.. _changes_7-0-0b1:

Version 7.0.0b1 — 2022-12-03

A number of changes have been made to file path handling, including pattern matching and path remapping with the [paths] setting (see :ref:config_paths). These changes might affect you, and require you to update your settings.

(This release includes the changes from 6.6.0b1 <changes_6-6-0b1_>_, since 6.6.0 was never released.)

• Changes to file pattern matching, which might require updating your configuration:

  • Previously, * would incorrectly match directory separators, making precise matching difficult. This is now fixed, closing issue 1407_.

  • Now ** matches any number of nested directories, including none.

• Improvements to combining data files when using the :ref:config_run_relative_files setting, which might require updating your configuration:

  • During coverage combine, relative file paths are implicitly combined without needing a [paths] configuration setting. This also fixed issue 991_.

  • A [paths] setting like */foo will now match foo/bar.py so that relative file paths can be combined more easily.

  • The :ref:config_run_relative_files setting is properly interpreted in more places, fixing issue 1280_.

• When remapping file paths with [paths], a path will be remapped only if the resulting path exists. The documentation has long said the prefix had to exist, but it was never enforced. This fixes issue 608, improves issue 649, and closes issue 757_.

• Reporting operations now implicitly use the [paths] setting to remap file paths within a single data file. Combining multiple files still requires the coverage combine step, but this simplifies some single-file situations. Closes issue 1212_ and issue 713_.

... (truncated)

Commits

• df3f2bf docs: latest sample HTML report
• 52b5680 docs: prep for 7.0.0
• be5f556 chore: make upgrade
• d20c1d0 docs: #1024 was also fixed
• 5feb451 chore: make upgrade
• 84749fd build: use tox.pip to ensure all tox pins are the same
• 3cd0bc6 test: this was wrong?
• c053b7f chore: make upgrade
• 7e0e072 build: a target to summarize make upgrade
• 18681c4 build: this link could be useful in the future
• 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 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)

[codecov-commenter]

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (e828e01) compared to base (1160bee).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #80   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           76        76           
  Branches        13        13           
=========================================
  Hits            76        76           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[dependabot]

Superseded by #81.