Automate PyPi package publishing #199
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
lubomir
reviewed
Feb 3, 2026
lubomir
reviewed
Feb 3, 2026
Contributor
|
In issue #173 there is an ask to create Github releases for each tag. Could that be automated with this workflow too? |
guillermodotn
force-pushed
the
deploy-pypi
branch
from
afbf794 to
4f9309c
Compare
guillermodotn
force-pushed
the
deploy-pypi
branch
from
4f9309c to
4a63903
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add workflow for building and publishing package into PyPi.
Part of: #194