You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
download-wheels can only find 50 names in numpy/staging, we need 52 #27185
I'm guessing this is done as part of the release process.
In my own projects I've had good success using the pypa/gh-action-pypi-publish action and trusted publishing on PyPI. This doesn't require long lasting tokens or username/password combos to be stored in a secret.
I have an action that gets triggered when there's an annotated tag (starting with 'v') pushed to the repo. The action builds all the wheels, makes an sdist, makes a GH release, then uses the trust publishing action to transfer all the wheels to PyPI. The automation takes a lot of potential mistakes out of the picture.
Only complication is that I don't know just yet how to do the trusted publishing from non-GH CI.
Activity
charris commentedon Aug 11, 2024
I was able to download the two missing files by hand, but it would be nice if everything just worked.
andyfaff commentedon Aug 12, 2024
I'm guessing this is done as part of the release process.
In my own projects I've had good success using the
pypa/gh-action-pypi-publishaction and trusted publishing on PyPI. This doesn't require long lasting tokens or username/password combos to be stored in a secret.I have an action that gets triggered when there's an annotated tag (starting with 'v') pushed to the repo. The action builds all the wheels, makes an sdist, makes a GH release, then uses the trust publishing action to transfer all the wheels to PyPI. The automation takes a lot of potential mistakes out of the picture.
Only complication is that I don't know just yet how to do the trusted publishing from non-GH CI.