This repository was archived by the owner on May 22, 2026. It is now read-only.
Auto-trigger release pipeline on main merge and add version check - #3335
Merged
Conversation
Yuchao Yan (msyyc)
requested review from
iscai-msft and
Chenjie Shi (tadelesh)
as code owners
February 6, 2026 04:58
ChenxiJiang333
approved these changes
Feb 6, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes
Why
This removes the manual step of triggering the release pipeline after a release PR is merged, making the release process more streamlined and less error-prone. The version check guard ensures the pipeline exits early if the versions are already published.