Repository navigation
Pause PyPI publishing until PUBLISH_PYPI is set - #19
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.
The publish job also bundles the installer and creates the GitHub release. A job-level condition would have skipped those on every tag; only the PyPI upload waits for PUBLISH_PYPI now.
The previous commit removed the job-level condition but did not add the step-level one (the step names itself before uses:), leaving PyPI publishing ungated. The upload step now carries the condition.
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. The
pypa/gh-action-pypi-publishstep inrelease.ymlnow runs only when the repository or org variablePUBLISH_PYPIistrue. The same job also bundlesinstaller.pyand creates the GitHub release, which still run on every tag (a job-level gate, in this PR's first commit, would have skipped them; the second commit moves it to the step). To resume, setPUBLISH_PYPI=true; no workflow change needed.