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.

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

⬆️ Bump coverage from 5.0 to 5.0.1 #52

Merged
merged 1 commit into from
Dec 23, 2019

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps coverage from 5.0 to 5.0.1.

Changelog

Sourced from coverage's changelog.

Version 5.0.1 --- 2019-12-22

  • If a 4.x data file is the cause of a "file is not a database" error, then use a more specific error message, "Looks like a coverage 4.x data file, are you mixing versions of coverage?" Helps diagnose the problems described in issue 886.
  • Measurement contexts and relative file names didn't work together, as reported in issue 899 and issue 900. This is now fixed, thanks to David Szotten.
  • When using coverage run --concurrency=multiprocessing, all data files should be named with parallel-ready suffixes. 5.0 mistakenly named the main process' file with no suffix when using --append. This is now fixed, closing issue 880.
  • Fixed a problem on Windows when the current directory is changed to a different drive (issue 895). Thanks, Olivier Grisel.
  • Updated Python 3.9 support to 3.9a2.
Commits
  • d2ae0e2 Prep for 5.0.1
  • 7e747a3 Re-order windows CI jobs to get more useful information earlier
  • 0d6a878 Detect when a 4.x data file is being read. #886
  • d66d496 Don't need to check for JSON-era bad-data messages any more
  • 77dc37f Tweak some coverage details of switch_context code
  • cecc5dd One more adjustment for Python 3.9a2
  • 28c29a7 bpo 39114 broke 3.9, but maybe it's their bug
  • 31f7280 Cleanup and changelog for #899 #900
  • ade1f2c fix context reporting for relative_files
  • 7dc3772 Python 3.9a2 reverted how argv[0] is handled
  • 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 use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [coverage](https://github.com/nedbat/coveragepy) from 5.0 to 5.0.1.
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](nedbat/coveragepy@coverage-5.0...coverage-5.0.1)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Upgrade or downgrade of project dependencies. label Dec 22, 2019
@codecov
Copy link

codecov bot commented Dec 22, 2019

Codecov Report

Merging #52 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   99.17%   99.17%           
=======================================
  Files           8        8           
  Lines         241      241           
=======================================
  Hits          239      239           
  Misses          2        2
Flag Coverage Δ
#unittests 99.17% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d5ead7...6e828b1. Read the comment docs.

@frenck frenck merged commit 099f506 into master Dec 23, 2019
@frenck frenck deleted the dependabot/pip/coverage-5.0.1 branch December 23, 2019 10:11
@github-actions github-actions bot locked and limited conversation to collaborators Mar 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Upgrade or downgrade of project dependencies.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant