Closed wesleybl closed 9 months ago
@mauritsvanrees does this commit have anything to do with this?
https://github.com/zestsoftware/zest.releaser/commit/8aed13ae84c0206569ad4026c6ada6a83994bc2d
@wesleybl Confirmed.
Well, my commit actually tries to restore previous behaviour, but it had no influence on the part that bites you, only on the parts that try to read [zest.releaser]
config from some files. Before this commit, there was a big restructuring, and some bits were lost.
I am making a PR.
BTW, I have six index-servers in my ~/.pypirc
, one of them named pypi
, and in my bash config I have export TWINE_REPOSITORY=pypi
. Then zest.releaser only uses this single index server, also with my new code.
BTW, I have six index-servers in my ~/.pypirc, one of them named pypi, and in my bash config I have export TWINE_REPOSITORY=pypi. Then zest.releaser only uses this single index server, also with my new code.
I tried in 9.0.0:
TWINE_REPOSITORY=nexus fullrelease
But it still asks for other repositories.
I tried it again and can confirm that
TWINE_REPOSITORY=nexus fullrelease
works. Cool!
Fix released in 9.1.1. Thanks for the report!
I have a project with the following
setup.cfg
:But when I run
fullrelease
on this project, I am asked if I want to upload it to all the servers that I have registered in.pypirc
.I'm using
zest.releaser 9.0.0
andpython 3.11
. It seems that in version8.0.0
this worked.