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

Update pytest to 3.2.0 #2153

Merged
merged 2 commits into from
Aug 2, 2017
Merged

Update pytest to 3.2.0 #2153

merged 2 commits into from
Aug 2, 2017

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Aug 1, 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 Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2153   +/-   ##
=======================================
  Coverage   97.09%   97.09%           
=======================================
  Files          39       39           
  Lines        7781     7781           
  Branches     1357     1357           
=======================================
  Hits         7555     7555           
  Misses        101      101           
  Partials      125      125

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 e2836d1...88d070d. Read the comment docs.

@asvetlov asvetlov merged commit fa0ef99 into master Aug 2, 2017
@asvetlov asvetlov deleted the pyup-update-pytest-3.1.3-to-3.2.0 branch August 2, 2017 05:58
@lock
Copy link

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants