chore(deps): update dependency coverage to v7.3.1 - abandoned #290
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.2.7
->7.3.1
Release Notes
nedbat/coveragepy (coverage)
v7.3.1
Compare Source
The semantics of stars in file patterns has been clarified in the docs. A
leading or trailing star matches any number of path components, like a double
star would. This is different than the behavior of a star in the middle of a
pattern. This discrepancy was
identified by Sviatoslav Sydorenko <starbad_>
, whoprovided patient detailed diagnosis <pull 1650_>
andgraciously agreed to a pragmatic resolution.
The API docs were missing from the last version. They are now
restored <apidocs_>
_... _apidocs: https://coverage.readthedocs.io/en/latest/api_coverage.html
.. _starbadhttps://github.com/nedbat/coveragepy/issues/1407#issuecomment-163108520909
.. _pull 165https://github.com/nedbat/coveragepy/pull/1650650
.. _changes_7-3-0:
v7.3.0
Compare Source
Added a :meth:
.Coverage.collect
context manager to start and stop coveragedata collection.
Dropped support for Python 3.7.
Fix: in unusual circumstances, SQLite cannot be set to asynchronous mode.
Coverage.py would fail with the error
Safety level may not be changed inside a transaction.
This is now avoided, closingissue 1646
_. Thanksto Michael Bell for the detailed bug report.
Docs: examples of configuration files now include separate examples for the
different syntaxes: .coveragerc, pyproject.toml, setup.cfg, and tox.ini.
Fix: added
nosemgrep
comments to our JavaScript code so thatsemgrep-based SAST security checks won't raise false alarms about security
problems that aren't problems.
Added a CITATION.cff file, thanks to
Ken Schackart <pull 1641_>
_... _pull 1641:https://github.com/nedbat/coveragepy/pull/16411
.. _issue 1646https://github.com/nedbat/coveragepy/issues/164646
.. _changes_7-2-7:
Configuration
📅 Schedule: 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.
This PR has been generated by Mend Renovate. View repository job log here.