Bump metadata version to 2.4 to fix license bug #2332
Conversation
When a project sets `license = { file = "LICENSE" }`, we're currently emitting a `License-File` entry, but Metadata-Version 2.3, which is invalid and now gets rejected by PyPI. This change bumps the metadata version.
Alternatively, we could only bump the version if license files are used and use the old `License` field for `license = { file = "LICENSE" }` again, but i'm not aware of any index currently rejecting metadata version 2.4.
|
this was a breaking change, twine does not allow metadata version 2.4: https://github.com/oconnor663/blake3-py/actions/runs/12079634972/job/33685800258 xref pypa/twine#1146 |
This was the version that built the a wheel package with Metadata-Version 2.3, which seems to be the larger version accepted by `pypa/gh-action-pypi-publish`, newer versions of `maturin`seem to be producing packages with Metadata-Version 2.4.
by pinning maturin to 1.7.5, we were able to push to pypi (twine check within pypa/gh-action-pypi-publish passes with metadata 2.3, and apparently pypi still accepts it). on a side note, pypa/twine#1123 was merged and as soon as that's released and propagated to pypa/gh-action-pypi-publish, your users should be green again using maturin 1.7.6. |
|
I think no action is required here: we're almost there ref pypa/gh-action-pypi-publish#308 |
|
pypa/[email protected] has been released with metadata 2.4 support 👍 |
When a project sets
license = { file = "LICENSE" }, we're currently emitting aLicense-Fileentry, but Metadata-Version 2.3, which is invalid and now gets rejected by PyPI, breaking publish for projects usinglicense = { file = "LICENSE" }. This change bumps the metadata version.Alternatively, we could only bump the version if license files are used and use the old
Licensefield forlicense = { file = "LICENSE" }again, but i'm not aware of any index currently rejecting metadata version 2.4.