Add workflow to push releases to pypi #665
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @eachanjohnson. I've add the pypi API key as I assume the only way to check it's all working is to merge this PR and then issue a test release? |
|
I did some digging. There's a test PyPI index at https://test.pypi.org/. I've added an untested workflow to upload to TestPyPI which is triggered when a tag is pushed, so you can check success before publishing the tag as a release. It requires an account on https://test.pypi.org/ and (Although tests are failing so it might need some tweaking). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This GitHub workflow will push new GH releases automatically to pypi. One caveat is that the pypi API key needs to be stored in the repository or organisation secrets (under Settings) as
PYPI_API_TOKEN.Relates to issue #663