Conversation
This will allow easy publishing to pypi. To cut a release, simply cut a new release on Github and this action will get triggered. Expects the secret `PYPI_PASSWORD`, the pypi API token, under `Settings->Secrets and Variables->Actions`, and click "New repository secret".
|
Thanks! That said, I'm not super enthusiastic about this in its current form. First, loopy releases are sufficiently infrequent that doing them manually is not a huge chore. Though I'm guessing that's something you're hoping to change? 🙂 At any rate, if there was to be automation, I would prefer it to be along the lines of what's in place for pytools. That has the advantage of using "Trusted Publishing" to PyPI so that there isn't an all-powerful credential floating around that could leak. It also allows PyPI to verify some details of the metadata it shows. |
Yep! :) In feinsum, I depend on loopy and would be preferred if the version on |
OK, I'll try to keep that in mind. 🙂 As before, feel free to ping me to request a release if it's been too long. |
2 participants
This will allow easy publishing to pypi. To cut a release, simply cut a new release on Github and this action will get triggered.
Expects the secret
PYPI_PASSWORD, the pypi API token, underSettings->Secrets and Variables->Actions, and click "New repository secret".(Feel free to close this if you already have an automated workflow.)