fix: change tag logic and verbose uv publish#1199
Merged
lucaseduoli merged 1 commit intomainfrom Mar 19, 2026
Merged
Conversation
github-actions
bot
added
ci
lucaseduoli
added a commit
that referenced
this pull request
Mar 19, 2026
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
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.
This pull request makes improvements to the nightly build and publishing process, primarily focusing on the PyPI nightly version tagging logic and the workflow for publishing to PyPI. The changes simplify and clarify the logic for generating nightly build versions, ensuring compliance with PEP 440, and enhance the publishing step for better reliability and debugging.
Nightly versioning logic improvements:
pypi_nightly_tag.pyto only check the local and main PyPI versions (removing redundant checks for the nightly version), and clarified how the nightly build number is determined, starting at.dev1and incrementing appropriately if a dev build already exists. [1] [2]Publishing workflow enhancements:
Publish to PyPIstep in.github/workflows/nightly-build.ymlto add strict error handling and verbose output for easier debugging and safer publishing.