Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump coverage from 6.3.3 to 6.4.2 #78

Closed
wants to merge 1 commit into from
Closed

Bump coverage from 6.3.3 to 6.4.2 #78

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 12, 2022

Bumps coverage from 6.3.3 to 6.4.2.

Changelog

Sourced from coverage's changelog.

Version 6.4.2 — 2022-07-12

  • Updated for a small change in Python 3.11.0 beta 4: modules now start with a line with line number 0, which is ignored. This line cannnot be executed, so coverage totals were thrown off. This line is now ignored by coverage.py, but this also means that truly empty modules (like __init__.py) have no lines in them, rather than one phantom line. Fixes issue 1419_.

  • Internal debugging data added to sys.modules is now an actual module, to avoid confusing code that examines everything in sys.modules. Thanks, Yilei Yang (pull 1399_).

.. _pull 1399: nedbat/coveragepy#1399 .. _issue 1419: nedbat/coveragepy#1419

.. _changes_6-4-1:

Version 6.4.1 — 2022-06-02

  • Greatly improved performance on PyPy, and other environments that need the pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick (pull 1381_ and pull 1388). Slightly improved performance when using the C trace function, as most environments do. Closes issue 1339.

  • The conditions for using tomllib from the standard library have been made more precise, so that 3.11 alphas will continue to work. Closes issue 1390_.

.. _issue 1339: nedbat/coveragepy#1339 .. _pull 1381: nedbat/coveragepy#1381 .. _pull 1388: nedbat/coveragepy#1388 .. _issue 1390: nedbat/coveragepy#1390

.. _changes_64:

Version 6.4 — 2022-05-22

  • A new setting, :ref:config_run_sigterm, controls whether a SIGTERM signal handler is used. In 6.3, the signal handler was always installed, to capture data at unusual process ends. Unfortunately, this introduced other problems (see issue 1310_). Now the signal handler is only used if you opt-in by setting [run] sigterm = true.

  • Small changes to the HTML report:

... (truncated)

Commits
  • 8ab9ff1 docs: latest sample HTML report
  • ee751cf docs: prep for 6.4.2
  • 413ccb7 build: run tests on nightly versions every day
  • d890bff docs: update the 3.11 version
  • 0d64498 fix: 3.11.0b4 has 0-numbered lines. Fixes #1419
  • 297b70e build: styfle/cancel-workflow-action@0.10.0 now accepts 'all'
  • ef25867 build(deps): bump actions/dependency-review-action from 1 to 2 (#1404)
  • b1f9cc0 build(deps): bump styfle/cancel-workflow-action from 0.9.1 to 0.10.0 (#1412)
  • f75d60a style: use new regex match object group access
  • 8447c99 test: copying pycache was causing race conditions, and was unneeded anyway.
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot
Bump coverage from 6.3.3 to 6.4.2
d52c3a1 
Bumps [coverage](https://github.com/nedbat/coveragepy) from 6.3.3 to 6.4.2.
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](nedbat/coveragepy@6.3.3...6.4.2)

---
updated-dependencies:
- dependency-name: coverage
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jul 12, 2022
@dependabot dependabot bot mentioned this pull request Jul 12, 2022
Closed
@will-henney
Copy link
Owner

will-henney commented Jul 21, 2022 via email

@dependabot dependabot bot closed this Jul 21, 2022
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 21, 2022

OK, I won't notify you about version 6.x.x again, unless you re-open this PR or update to a 6.x.x release yourself.

@dependabot dependabot bot deleted the dependabot/pip/coverage-6.4.2 branch July 21, 2022 00:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@will-henney