-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Update requirements lock to use twine v6 #308
Comments
cc @webknjaz @woodruffw :) |
I can send a PR for @webknjaz to review later today. It's worth noting that release v6 doesn't have "full" support for metadata 2.4 quite yet; it just suppresses the outright failures that happened in earlier versions. But IMO that's an improvement in the status quo, versus having new builds fail entirely. |
#309 performs the bump. I'll send a separate bump PR when the (upcoming) twine release that handles 2.4 more thoroughly is ready. |
Please please can we have a new release including this fix. |
xref #313 |
Thanks for the nudges! I've started the required activities and the pessimistic ETA is an hour, but realistically it should be out much sooner. |
UPD: I've pushed the tag 44 minutes ago so it's usable and people on |
@ddelange @samuelcolvin v1.12.3 is fully out: #314. Enjoy! |
Amazing, thanks so much! |
Hi 👋
twine v6 was released, allowing metadata v2.4 via pypa/twine#1123. Could you update the lockfiles and cut a release?
The text was updated successfully, but these errors were encountered: