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.2.1 to 5.3 #267

Merged
merged 1 commit into from Sep 14, 2020

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps coverage from 5.2.1 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.
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.
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.

If all status checks pass Dependabot will automatically merge this pull request during working hours.


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 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 the .dependabot/config.yml file in this repo:

  • Update frequency
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • 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.2.1 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.2.1...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 64.583% when pulling 120479f on dependabot/pip/coverage-5.3 into 5c4e305 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 64.583% when pulling 120479f on dependabot/pip/coverage-5.3 into 5c4e305 on master.

@dependabot-preview dependabot-preview bot merged commit fa5079b into master Sep 14, 2020
@dependabot-preview dependabot-preview bot deleted the dependabot/pip/coverage-5.3 branch September 14, 2020 06:00
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.

None yet

1 participant