-
Notifications
You must be signed in to change notification settings - Fork 13
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
Supported PyPI trusted publishers #136
Comments
I think we need to wait for pypi/warehouse#11096 to be closed before this will work in the reusable workflows unfortunately. Once it is, adding what you have above to the upload job in each publish workflow should be all that is needed. The |
Any update on this? Has the situation changed? PyPA merged the recommendations into https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/ |
Last I checked (a couple of weeks ago) it's still unsupported upstream. |
Looks like if you forked the templates into the same org you could maybe make it work: pypi/warehouse#11096 (comment) |
Saw the github notifications about trusted publishers while building |
AFAIK PyPI has not implemented the support yet. This issue is still unresolved: |
yep we are waiting for upstream support. Apparently it's being worked on currently. |
Thanks, both! Funny that github is pushing it so much if it only half works... |
APLpy has started erroring on upload to PyPI because of this:
https://github.com/aplpy/aplpy/actions/runs/11846325120/job/33013937737 Is there any workaround at this point? |
Should we perhaps change the workflows to use |
I think you have to disable trusted publishing if you use the workflow from here, for now. |
@pllim - how does one do this? |
See https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/, https://docs.pypi.org/trusted-publishers/using-a-publisher/.
To support trusted publishers, add this to the
pypa/gh-action-pypi-publish
step:Perhaps a boolean flag to turn this on or off?
The text was updated successfully, but these errors were encountered: