-
Notifications
You must be signed in to change notification settings - Fork 39
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
Update Release action #165
Comments
Could consider automatizing the pypi publication via github actions, see e.g. here in that example, pypi upload is triggered automatically when a new tag is pushed. Just have to figure out how to make sure that it only triggers when the new tag the master (to avoid people randomly tagging stuff) |
OK, I'll try to look into this next week. I think I found something in this direction somewhere else that protects us from all the pitfalls. |
For some other HEPData packages (hepdata-cli, hepdata-converter, hepdata-validator, hepdata-converter-ws, hepdata-converter-ws-client), we trigger a PyPI upload via GitHub Actions by making a GitHub Release. This method might work for |
To fix this eventually, follow https://til.simonwillison.net/pypi/pypi-releases-from-github |
I'm already using PyPI's trusted publishing for the other HEPData repositories, so I can take a look if you get stuck. By the way, could you please add user "hepdata" as a Maintainer or Owner of |
Invite sent. |
minor
The text was updated successfully, but these errors were encountered: