Separate PyPI publishing from package CI - #283
Merged
Merged
Conversation
Contributor
|
This was referenced Aug 11, 2026
Merged
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
1 participant
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.
What changed
uv publishfrom the ordinary package CI workflowmainWhy
The Great Docs merge correctly kept package version
0.1.28, but ordinary CI attempted to republish that immutable PyPI version and failed with HTTP 400 because the wheel already exists.Publishing should be handled by an intentional release/tag workflow rather than every push to
main. Adding or redesigning that release automation is deliberately outside this focused fix.Validation
The previous failed run completed installation, package build, and all 10 tests successfully; only the PyPI re-upload failed.