Set up publishing to PyPI via GitHub Actions #40
Merged
Conversation
This file contains hidden or 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
fnesveda
added
enhancement
mnmkng
approved these changes
May 13, 2021
Member
mnmkng
left a comment
mnmkng
left a comment
There was a problem hiding this comment.
The workflow looks good to me 👍
mhamas
approved these changes
May 14, 2021
mtrunkat
added
capitalized
fnesveda
added
the
validated
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.
I've set up publishing of this package to PyPI via GitHub Actions. It works similarly as the publishing of
apify-client-jsto NPM:src/apify_client/_version.pymaster, a new beta release is created and published to PyPI, automatically appending a beta number to the version, incrementing the beta number from the last published beta release for the current versionsrc/apify_client/_version.pywas already published, the publication failsCHANGELOG.mdwas not updated for the published version, the publication failsIt's pretty hard to test this properly live without polluting the PyPI listing for this package, but I've tested and debugged this exact same release process on TestPyPI with a dummy package in a private repo, and everything worked fine, so I'm reasonably confident this will work too.