Add PyPI publishing workflow - #4
Merged
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
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.
Summary
Publishworkflow for PyPI trusted publishing.twine check --strictbefore publishing.v*tag, then GitHub Actions publishes through thepypienvironment.0.2.0.Packaging decision
This publishes only CUDA 12.8 wheels under
qwentts-cpp-pythonfor now. The repo still builds CPU and CUDA 13 wheels as validation artifacts, but uploading CPU, CUDA 12.8, and CUDA 13 wheels under the same distribution name/version/platform tag would leave pip with no reliable way to choose the desired runtime.CUDA 12.8 is the safest default public wheel target because it is the compatibility target we want faster-qwen3-tts users to install by default.
Validation
qwentts-cpp-pythonis not currently published on PyPI withpython3 -m pip index versions qwentts-cpp-python..github/workflows/publish.ymland.github/workflows/wheels.ymlwith PyYAML.pyproject.tomlversion andsrc/qwentts_cpp/__init__.py__version__both read0.2.0.uv run --with pytest pytest -qgit diff --cached --checkFollow-up before first tag
Configure the PyPI trusted publisher for the
pypiGitHub environment and theandimarafioti/qwentts-cpp-pythonrepository. Then the first release should be publishable by pushing an annotatedv0.2.0tag frommain.