Release 1.11.0

[brainwane]

I'm preparing to release version 1.11.0 at the moment.

I have a tag up for it. I've put 1.11.0rc1 up on Test PyPI and, after testing, on PyPI. I've done approximately all the testing folks recommended in #314.

I'm waiting till Monday or Tuesday to put out a full release, but @di I figured this'd be good enough for you to test with as you work on pypi/warehouse#869 (comment) .

[codecov]

Codecov Report

Merging #321 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #321   +/-   ##
=======================================
  Coverage   69.55%   69.55%           
=======================================
  Files          12       12           
  Lines         588      588           
  Branches       93       93           
=======================================
  Hits          409      409           
+ Misses        151      150    -1     
- Partials       28       29    +1

Impacted Files	Coverage Δ
twine/__init__.py	100% <100%> (ø)	⬆️
twine/wininst.py	29.72% <0%> (ø)	⬆️

---

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 1e7d2ff...ebb0dda. Read the comment docs.

[di]

Thanks! Don't feel like this is blocking me, I can do all the testing I need with or without a release.

[sigmavirus24]

What are the changes in 1.11.0?

[brainwane]

• better "register" guidance and pypi.org migration advice #320 Remove PyPI as default register package index.
• Add Metadata 2.1 #319 Support Metadata 2.1 (PEP 566), including Markdown for description fields.
• Update PyPI URLs and simplify contributor instructions #318 Update PyPI URLs.

[brainwane]

Also:

• Raise exception if attempting upload to deprecated legacy PyPI URLs  #322: Raise exception if attempting upload to deprecated legacy PyPI URLs.
• New maintainer release checklist #314: Add new maintainer, release checklists.
• No documentation on using keyring? #277: Add instructions on how to use keyring.

[brainwane]

And #269 Avoid uploading to PyPI when given alternate repository URL.

[brainwane]

Works fine with zest.releaser and with devpi. Am running into some errors when I run tox -e pre_twine. Will investigate tonight.

[brainwane]

@mplanchard if you have time before I do to look at the tox errors that happen when I run tox -e pre_twine on twine master and/or this branch, let me know?

[mplanchard]

@brainwane py27-py36 are working just fine for me. What errors are you getting?

Edit: the version of twine they are downloading is twine-1.11.0rc1. Is that correct?

[brainwane]

@mplanchard I'm sorry. I should have just run tox which would run on the current branch (I'd used pip install -e . in the Twine repo to keep it installed), rather than testing 1.11.0rc1. My fault. I ran tox -e py36 and it ran fine, so now I'm just waiting for the rest of the tox tests to run and I think everything is sorted out.

[mplanchard]

Awesome! Glad to hear it. The test_server tests, unfortunately, take quite a while! I've been meaning to figure out how to speed them up for some time.