-
-
Notifications
You must be signed in to change notification settings - Fork 469
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
twine issue due to recent release of importlib-metadata #1180
Comments
Thanks for the clear report! Sounds like Line 51 in 03d535d
|
what the way to bump twine version in rye project? |
I can confirm that the fix from @geodab works. My Github actions failed due this bug, but I was able to publish my package locally from my machine. |
If anyone are having issues in their Github actions when publishing packages using Rye, I added an additional step that patches Rye with the update Twine and it works fine for me. Consider this is temporary patch though. It uses the environmental variable from - name: Set up Rye
uses: eifinger/setup-rye@v3
- name: Patch Rye
run: |
echo "Patching Rye with Twine 5.1.1"
$RYE_HOME/self/bin/pip install twine==5.1.1 |
It seems that a recent major release of importlib_metadata 8.0.0 removed deprecated support that twine 4.0.2 relies upon, which causes twine (and rye publish) to fail to run. See astral-sh/rye#1180 for more details
Steps to Reproduce
It seems that a recent major release of importlib_metadata 8.0.0 removed deprecated support that twine 4.0.2 relies upon, which causes twine (and rye publish) to fail to run.
The simplest way to reproduce is to run
~/.rye/self/bin/twine --version
.The error can be fixed by either downgrading importlib_metadata to 7.2.1 or upgrading twine to 5.1.1, e.g., by running either
~/.rye/self/bin/pip install importlib_metadata==7.2.1
or~/.rye/self/bin/pip install twine==5.1.1
.Additional details and explanation can be found at pypa/twine#1125 and abichinger/semantic-release-pypi#39.
Expected Result
Either:
Or:
Actual Result
Version Info
Stacktrace
No response
The text was updated successfully, but these errors were encountered: