Repository navigation
Pause PyPI publishing until PUBLISH_PYPI is set - #13
Merged
Merged
Conversation
The owner has paused all PyPI publishing until further notice. Each job that uploads to PyPI now runs only when the repository or org variable PUBLISH_PYPI is 'true'; tags still build and publish the GitHub release.
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.
Owner decision (2026-10-06): nothing is published to PyPI until further notice. Every job that uploads to PyPI in
.github/workflows/release.ymlnow hasif: vars.PUBLISH_PYPI == 'true'(combined with any existing condition). The variable is unset, so a tag still builds and creates the GitHub release but skips PyPI. To resume, setPUBLISH_PYPI=trueas a repository or org variable; no workflow change is needed.