Failed to publish to PyPI: InvalidDistribution: Metadata is missing required fields: Name, Version

[zhuchcn]

I got this error when a new release was made on moPepGen.

https://github.com/uclahs-cds/package-moPepGen/actions/runs/15168004756/job/42650781778#step:4:37

Checking dist/mopepgen-1.4.6-py3-none-any.whl: ERROR    InvalidDistribution: Metadata is missing required fields: Name,        
         Version.                                                               
         Make sure the distribution includes the files where those fields are   
         specified, and is using a supported Metadata-Version: 1.0, 1.1, 1.2,   
         2.0, 2.1, 2.2, 2.3.    

I do have name and version in metadata. Do the keys need to be capitalized now?

https://github.com/uclahs-cds/package-moPepGen/blob/ab02bd80deafe07e13fc66a0883ef770878c70ac/setup.cfg#L1-L16

[aholmes]

Taking a look.

[aholmes]

This looks like an issue with the 1.8 version of gh-action-pypi-publish that tool-pypi-publish-action/publish-to-pypi uses.

With version 1.8 I can reproduce the error using the dependencies of that action.

$ python -m build
...
$ python -m twine upload dist/mopepgen-1.5.0*
Uploading distributions to https://upload.pypi.org/legacy/
ERROR    InvalidDistribution: Metadata is missing required fields: Name, Version.
         Make sure the distribution includes the files where those fields are specified, and is using a supported Metadata-Version: 1.0, 1.1, 1.2, 2.0, 2.1, 2.2, 2.3.

When using the dependencies for version 1.12 (latest), twine succeeds.

$ python -m twine upload dist/mopepgen-1.5.0*
Uploading distributions to https://upload.pypi.org/legacy/
Uploading mopepgen-1.5.0-py3-none-any.whl
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 285.9/285.9 kB • 00:00 • 567.1 kB/s
WARNING  Error during upload. Retry with the --verbose option for more details.
ERROR    HTTPError: 403 Forbidden from https://upload.pypi.org/legacy/
         The user 'aholmes' isn't allowed to upload to project 'mopepgen'. See https://pypi.org/help/#project-name for more information.

(the 403 is expected here)

I will update tool-pypi-publish-action to use v1 instead of the more specific v1.8. Hopefully allowing the latest "minor" version avoids this kind of issue in the future without introducing breaking changes.

[aholmes]

Fixed in the action. 7b9124d

I will update the version moPepGen is using.

[aholmes]

Unfortunately this seems to be caused by some insanity when the pypi action is used through nested or compound actions. The latest pypi actions build a docker image, which then ends up with the wrong repository URL due to a "will not fix" bug in the actions.

pypa/gh-action-pypi-publish#300
actions/runner#2185 (comment)
pypa/gh-action-pypi-publish#304
pypa/gh-action-pypi-publish#302
pypa/gh-action-pypi-publish#299 (comment)

The fix for this issue is to not use uclahs-cds/tool-pypi-publish-action, and to instead use pypa/gh-action-pypi-publish directly. See uclahs-cds/package-moPepGen#915 for more information.