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

Update tox to 3.7.0 #78

Merged
merged 2 commits into from Feb 16, 2019

Conversation

Projects
None yet
2 participants
@pyup-bot
Copy link
Contributor

pyup-bot commented Jan 12, 2019

This PR updates tox from 3.6.0 to 3.7.0.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

@pyup-bot pyup-bot referenced this pull request Jan 12, 2019

Closed

Update tox to 3.6.1 #73

@codecov

This comment has been minimized.

Copy link

codecov bot commented Jan 12, 2019

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #78   +/-   ##
=======================================
  Coverage   81.81%   81.81%           
=======================================
  Files          45       45           
  Lines        1848     1848           
=======================================
  Hits         1512     1512           
  Misses        336      336

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 0ed4995...2be607b. Read the comment docs.

@omercnet omercnet merged commit a34e17f into master Feb 16, 2019

4 checks passed

codecov/patch Coverage not affected when comparing 0ed4995...2be607b
Details
codecov/project 81.81% remains the same compared to 0ed4995
Details
guardrails/scan no new security issues detected
Details
security/snyk - requirements.txt (Cymmetria) No known issues
Details

@wafflebot wafflebot bot removed the in progress label Feb 16, 2019

@omercnet omercnet deleted the pyup-update-tox-3.6.0-to-3.7.0 branch Feb 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment