Skip to content

Update pytest to 3.2.0 #61

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

Merged
merged 1 commit into from
Aug 2, 2017
Merged

Update pytest to 3.2.0 #61

merged 1 commit into from
Aug 2, 2017

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Aug 2, 2017

There's a new version of pytest available.
You are currently using 3.1.3. I have updated it to 3.2.0

These links might come in handy: PyPI | Changelog | Repo | Homepage

I couldn't find a changelog for this release. Do you know where I can find one? Tell me!

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

@codecov-io
Copy link

codecov-io commented Aug 2, 2017

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #61   +/-   ##
=======================================
  Coverage   79.97%   79.97%           
=======================================
  Files           8        8           
  Lines         844      844           
=======================================
  Hits          675      675           
  Misses        169      169

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 bc611d8...cecf466. Read the comment docs.

@tony tony merged commit 70a92d0 into master Aug 2, 2017
@tony tony deleted the pyup-update-pytest-3.1.3-to-3.2.0 branch August 2, 2017 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants