ci/docs: add release workflow (publish to pypi) and a RELEASE.md file #32
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
consideRatio
changed the title
|
Is there something I should do to move this forward? :D |
|
Review merge :) |
|
Done :) |
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.
PR Summary
PYPI_PASSWORDis added already, based on a deployment token for our PyPI bot account now with maintainer permissions for the associated PyPI project.Related
It would be nice to retroactively add tags to the commits associated with the previous releases and push those before merging this to avoid triggering workflows that would try publish to PyPI. If that is done later, they won't override any PyPI release though because the upload command looks like this:
twine upload --skip-existing dist/*