-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Release of new version failing #1308
Comments
Solves #1308 As described on linked issue, the problem may be solved by using packaging=24.2 and twine=6.10
Solves #1308 As described on linked issue, the problem may be solved by using packaging=24.2 and twine=6.10
Also, fix(requirements.txt): update requirement to fix pypi deployment Solves #1308 As described on linked issue, the problem may be solved by using packaging=24.2 and twine=6.10
Also, fix(requirements.txt): update requirement to fix pypi deployment Solves #1308 As described on linked issue, the problem may be solved by using packaging=24.2 and twine=6.10
Also, fix(requirements.txt): update requirement to fix pypi deployment Solves #1308 As described on linked issue, the problem may be solved by using packaging=24.2 and twine=6.10
just setting the versions in requirements.txt did not work
It seems that the packaging requirement is not met; From the actions log
|
Also, fix(requirements.txt): update requirement to fix pypi deployment Solves #1308 As described on linked issue, the problem may be solved by using packaging=24.2 and twine=6.10
Also, fix(.github.pypi.yml): update requirement to fix pypi deployment Solves #1308
Also, fix(.github.pypi.yml): update requirement to fix pypi deployment Solves #1308
From the cited twine issue, I tried updating the
the requirements.txt file belongs to the second step; but we actually needed to update the
|
This was annoying. Thanks for dealing with it! |
I was trying to release a new juriscraper version, and the deploy action has an error
This has been reported by other people here pypa/twine#1216 (comment) and the solution seems to be using specific versions of
twine
andpackaging
packagesThe text was updated successfully, but these errors were encountered: