Repository navigation
ci(release): one-time self-hosted PyPI recovery for v4.20.0 - #317
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.
Purpose
Permit a one-time v4.20.0 PyPI publication from the reviewed self-hosted Linux pool while GitHub-hosted Actions and artifact storage are unavailable. The owner explicitly approved the manual release exception.
Guardrails
manual_self_hostedinput defaults to false; release-published events keep the hosted route.mainwith the exactv4.20.0tag passes the recovery guard.pypi-productionenvironment still requires owner review, and the existing PyPI trusted publisher receives a short-lived GitHub OIDC identity.The normal protected workflow remains unchanged by default. Remove this one-time option after the release.