You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm one of the maintainers of Twine. I was checking out the libraries.io usage list for twine and happened to notice that your requirements.txt file specifies an old version. The new version of Twine is 1.10.0. Anything we can do to make your upgrade path easier?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @brainwane, thanks for reaching out. I guess I'm technically the maintainer of git-cc, but I haven't used it in over 7 years so I basically just accept patches from people. I'm afraid to say there is no testing in git-cc so it's fairy hard to change anything without having a live clearcase server to test against. :(
@charleso OK, I understand. I see that twine is not actually used anywhere in your codebase; it's used by zest.releaser, a tool the maintainer can use to upload the package to PyPI. So upgrading Twine and zest.releaser won't affect the ClearCase-related code at all.
Twine's now at version 1.11.0 (changelog). And zest.releaser is at 6.15.0. I encourage you to upgrade and to use Test PyPI to try uploading your package to PyPI with the new tooling!
Hi! I'm one of the maintainers of Twine. I was checking out the libraries.io usage list for twine and happened to notice that your
requirements.txt
file specifies an old version. The new version of Twine is 1.10.0. Anything we can do to make your upgrade path easier?Thanks!
The text was updated successfully, but these errors were encountered: