Removal manual gates from deployment process#3830
Merged
Conversation
DrJosh9000
reviewed
Apr 20, 2026
zhming0
force-pushed
the
ming/removal-manual-gates-from-deployment-process
branch
from
692cba1 to
84d9089
Compare
DrJosh9000
approved these changes
Apr 20, 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.
Remove the
block: "beta?"andblock: "stable?"manual gates from the release pipeline, so the release flow proceeds automatically: edge → beta → stable.Why
We never use these manual gates, every release we just click through them. The pipeline already has sufficient safeguards:
mainor*-*-stablebranches