AST-171789 Gate release and delete jobs behind release environment - #222
Merged
Merged
Conversation
…nment Both the release job and the delete-packages-and-releases job could run without any approval gate, even though the destructive delete workflow is directly dispatchable and is also invoked by release.yml. Adding `environment: release` to each job routes them through the existing `release` GitHub Environment, which already has required reviewers and a branch policy configured. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cx-rakesh-kadu
approved these changes
Aug 31, 2026
cx-sumit-morchhale
self-requested a review
August 31, 2026 10:59
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.
Adds
environment: releaseto the release job and to the delete-packages-and-releases job, both of which previously ran with no approval gate.The delete workflow removes GitHub releases, tags, and npm package versions, and is directly dispatchable, so it needed the same gate as release.yml, which calls it as a reusable workflow.
Dev-build cleanup runs will now pause for approval, which is the intended behavior.