Closed dkopelove closed 1 year ago
Could you try again with the latest version of zest.releaser?
We're calling twine on a much higher level now, so there is a big chance that twine gets to do its TWINE_CERT
thing. We're not calling individual functions anymore, but basically the main run()
method (or whatever the name).
I'm assuming this to be fixed.
Hello,
Per the documentation, it's recommended that a user specifies the environment variable TWINE_CERT in order to have twine use a specific ca cert bundle for verification when uploading distributions (src, wheel).
Unfortunately, zest.releaser is hooking into twine in such a fashion that environmental variables are not evaluated.
This is to request some way of getting this capability of twine pulled out so that it can be specified when calling zest.releaser.
Thanks, dan