-
-
Notifications
You must be signed in to change notification settings - Fork 316
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
400 response, no error message #1786
Comments
I'm getting a related error when attempting to publish to pypi today: updating the the METADATA file to 'version 2.4' did not resolve it. |
I'm looking into this, will be fixed by the end of the day |
Any update on this? I'm getting the same problem. |
Working on this today |
I see that this is patched. I've installed hatchling and hatch from a fresh pull from git, but I'm still getting the error. What's the correct way to get this update? hatch --version reports "Hatch, version 1.12.1.dev29" |
There has not yet been a release, working on that still |
Is there any mitigation or workaround presently? This is preventing me from publishing some updates to packages. |
The new release of Hatchling is out now https://github.com/pypa/hatch/releases/tag/hatchling-v1.26.0 |
@ofek this is still an issue with the new release... |
The error from @sjayjam is definitely fixed if you use the latest version of Hatchling. Is your issue unrelated to that? |
This may be a separate error, but this is what I'm still experiencing on the latest version (the package, in case it's helpful): $ hatch publish
dist/strptime_cli-0.2.0.tar.gz ... failed
Error uploading to repository: https://upload.pypi.org/legacy/ - Client error '400 license-expression introduced in metadata version 2.4, not 2.3. See https://packaging.python.org/specifications/core-metadata for more information.' for url 'https://upload.pypi.org/legacy/'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400 I did a My version: $ hatch --version
Hatch, version 1.13.0 |
You would have to clear the pip cache or require |
That worked for me. Thanks! |
Seems to be solved ! |
just get this trying to upload to test pypi, twine works fine... : ' (
The text was updated successfully, but these errors were encountered: