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 twine to 1.9.1 #1928

Merged
merged 2 commits into from
May 27, 2017
Merged

Update twine to 1.9.1 #1928

merged 2 commits into from
May 27, 2017

Conversation

pyup-bot
Copy link
Contributor

There's a new version of twine available.
You are currently using 1.9.0. I have updated it to 1.9.1

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

Changelog

1.9.1

  • Blacklist known bad versions of Requests. See also 🐛253

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 #1928 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1928   +/-   ##
=======================================
  Coverage   97.05%   97.05%           
=======================================
  Files          37       37           
  Lines        7610     7610           
  Branches     1328     1328           
=======================================
  Hits         7386     7386           
  Misses        101      101           
  Partials      123      123

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 c96322c...7552059. Read the comment docs.

@asvetlov asvetlov merged commit f280017 into master May 27, 2017
@asvetlov asvetlov deleted the pyup-update-twine-1.9.0-to-1.9.1 branch May 27, 2017 19:20
@lock
Copy link

lock bot commented Oct 29, 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 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 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