Repository navigation
ci(publish): Update pypa/gh-action-pypi-publish to v1.14.2 - #87
Conversation
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Up to standards ✅🟢 Issues
|
Summary
The v0.0.31 PyPI upload failed (run 37954132245):
python-publish.ymlpinspypa/gh-action-pypi-publishto v1.4.2 (2021). That action installs twine 6.2.0, which accepts metadata versions only up to 2.4. hatchling 1.32 writes Metadata-Version 2.5, so the metadata check fails. v0.0.30 was built with hatchling 1.29, which still wrote 2.4.This PR updates the action to v1.14.2 (pinned by commit), which uses twine 7.0.0 and packaging 26.2. The
user,passwordandverboseinputs are unchanged.Verification
Built the package locally with hatchling 1.32.4 (Metadata-Version 2.5):
twine check --strictpassed for the wheel and the sdist.After merging
A release run uses the workflow file from the tagged commit, so re-running the failed run will not help. After this change reaches
main, re-tag v0.0.31 on the newmaincommit and publish the release again, or release 0.0.32.