-
Notifications
You must be signed in to change notification settings - Fork 224
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
Fix the "Publish to PyPI" workflow #3736
Comments
Agree with option 2, even though it's a bit more work to rewrite the workflow. Could you also remove the 'Temporary token for PyGMT' used for the PyGMT v0.14.0 release? |
Did you remove it already? |
No, I don't think I can remove it since you created it. |
Originally posted by @seisman in #3691 (comment)
Btw, it looks like the manual PyPI upload at https://pypi.org/project/pygmt/0.14.0/#pygmt-0.14.0-py3-none-any.whl is bigger (428.4 kB) than the one on TestPyPI at https://test.pypi.org/project/pygmt/#pygmt-0.14.0-py3-none-any.whl (290.1 kB) for PyGMT v0.14.0:
Looking inside the |
I can't see the token now. Maybe I've removed it after uploading the release? |
Just tried to run |
Yeah, I get the same on my side running |
See #3691 (comment) for details.
Generally speaking, we have the following options:
attestations: false
Producing attestations fails when attempting publishing from unsupported reusable workflows (when enabled) pypa/gh-action-pypi-publish#283 (comment)I think we should go for option 2, since it is recommended in the official packaging guides at https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#separate-workflow-for-publishing-to-testpypi
The text was updated successfully, but these errors were encountered: