Use 'none' environment for auto-release publish#48235
Open
raych1 wants to merge 1 commit into
Open
Conversation
…al gate Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c896e16a-4a37-45eb-9f29-3b5d0cf3375b
|
Azure Pipelines: Successfully started running 1 pipeline(s). 9 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Routes automated post-merge releases around the manual approval gate while preserving manual release behavior.
Changes:
- Uses the approval-free
noneenvironment for auto-release runs onmain. - Retains the configured publish environment for all other releases.
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.
What
The package publish deployment now targets the
noneenvironment for auto-release runs.Why
Auto-release is the fully automated post-merge CI flow on
main; a manual approval gate would block it.Impact
Manual releases are unaffected and continue to use the existing approval-gated publish environment. The
noneenvironment must be, or will be auto-created as, an Azure DevOps environment with no approvals/checks.