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.3 to 5.3 #481

Closed
wants to merge 1 commit into from

Conversation

dependabot-preview[bot]
Copy link

Bumps coverage from 5.0.3 to 5.3.

Release notes

Sourced from coverage's releases.

coverage-5.3

  • The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
  • If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011. This is now fixed.

coverage-5.2.1

  • The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009). This is now fixed.
  • The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960).

coverage-5.2

  • The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858 and pull request 931).
  • The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982).
  • The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779 and pull request 932).
  • The --skip-empty option is now available for the XML report, closing issue 976.
  • The coverage report command now accepts a --sort option to specify how to sort the results. Thanks, Jerin Peter George (pull request 1005).
  • If coverage fails due to the coverage total not reaching the --fail-under value, it will now print a message making the condition clear. Thanks, Naveen Yadav (pull request 977).
  • TOML configuration files with non-ASCII characters would cause errors on Windows (issue 990). This is now fixed.
  • The output of --debug=trace now includes information about how the --source option is being interpreted, and the module names being considered.

coverage-5.1

coverage-5.0.4

  • If using the [run] relative_files setting, the XML report will use relative files in the <source> elements indicating the location of source code. Closes issue 948.
  • The textual summary report could report missing lines with negative line numbers on PyPy3 7.1 (issue 943). This is now fixed.
  • Windows wheels for Python 3.8 were incorrectly built, but are now fixed. (issue 949)
  • Updated Python 3.9 support to 3.9a4.
  • HTML reports couldn’t be sorted if localStorage wasn’t available. This is now fixed: sorting works even though the sorting setting isn’t retained. (issue 944 and pull request 945). Thanks, Abdeali Kothari.
Changelog

Sourced from coverage's changelog.

Version 5.3 --- 2020-09-13

  • The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
  • If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011. This is now fixed.

Version 5.2.1 --- 2020-07-23

  • The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009). This is now fixed.
  • The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960).

Version 5.2 --- 2020-07-05

  • The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858 and pull request 931).
  • The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982).
  • The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779 and pull request 932).
  • The --skip-empty option is now available for the XML report, closing issue 976.
  • The coverage report command now accepts a --sort option to specify how to sort the results. Thanks, Jerin Peter George (pull request 1005).
  • If coverage fails due to the coverage total not reaching the --fail-under value, it will now print a message making the condition clear. Thanks, Naveen Yadav (pull request 977).
  • TOML configuration files with non-ASCII characters would cause errors on Windows (issue 990). This is now fixed.
  • The output of --debug=trace now includes information about how the --source option is being interpreted, and the module names being considered.

Version 5.1 --- 2020-04-12

  • The JSON report now includes counts of covered and missing branches. Thanks, Salvatore Zagaria.
  • On Python 3.8, try-finally-return reported wrong branch coverage with decorated async functions (issue 964). This is now fixed. Thanks, Kjell Braden.
  • The ~coverage.Coverage.get_option and ~coverage.Coverage.set_option methods can now manipulate the [paths] configuration setting. Thanks to Bernát Gábor for the fix for issue 967.

Version 5.0.4 --- 2020-03-16

  • If using the [run] relative_files setting, the XML report will use relative files in the <source> elements indicating the location of source code. Closes issue 948.
  • The textual summary report could report missing lines with negative line numbers on PyPy3 7.1 (issue 943). This is now fixed.
  • Windows wheels for Python 3.8 were incorrectly built, but are now fixed. (issue 949)
  • Updated Python 3.9 support to 3.9a4.
  • HTML reports couldn't be sorted if localStorage wasn't available. This is now fixed: sorting works even though the sorting setting isn't retained. (issue 944 and pull request 945). Thanks, Abdeali Kothari.
Commits
  • d13594e Making a release
  • 039ef09 If a plugin is disabled, don't try to record its file tracers. #1011
  • 24eb6fd Move disable_plugin to Python
  • 987ceb9 Fix a missed exception handling for bad plugins
  • c907b2e ambigious -> ambiguous
  • 263f3e1 Docs and cleanup for source_pkgs
  • ecd6ab1 Create Way to force package even if filepath exists (#1026)
  • 39e6d1d Thomas Grainger's first commit
  • 154f528 replace confusing comment with assertion (#1028)
  • c315908 Explain a mystery
  • 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.3 to 5.3.
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](nedbat/coveragepy@coverage-5.0.3...coverage-5.3)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Sep 14, 2020
@coveralls
Copy link

Coverage Status

Coverage remained the same at 42.065% when pulling 131678d on dependabot/pip/coverage-5.3 into 10a4d82 on master.

@dependabot-preview
Copy link
Author

Superseded by #527.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/coverage-5.3 branch December 21, 2020 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant