You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Switch stable pipeline trigger to release branch only (#1003)
Trigger on pushes to release/* branches instead of tag pushes.
This prevents the pipeline from firing on tags pushed to main.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The stable release pipeline triggers automatically when the release branch is pushed to upstream.
70
72
71
73
> ✋ **Confirm**: Is the release branch pushed to upstream?
72
74
@@ -98,9 +100,9 @@ Goal: Keep `main` moving forward on an odd minor with `-dev` suffix.
98
100
99
101
---
100
102
101
-
### Phase 4 — Tag and trigger the pipeline
103
+
### Phase 4 — Tag the release
102
104
103
-
Goal: Push a tag from the release branch to trigger the stable pipeline.
105
+
Goal: Tag the release commit for GitHub release tracking.
104
106
105
107
Replace `release/2026.4` and `v2026.4.0` with the actual branch and version:
106
108
```
@@ -111,11 +113,11 @@ git tag v2026.4.0
111
113
git push upstream v2026.4.0
112
114
```
113
115
114
-
The pipeline triggers automatically on the new tag. Navigate to the stable pipeline in Azure DevOps to monitor the run.
116
+
The tag marks the release for GitHub. The pipeline was already triggered by the release branch push in Phase 2. Navigate to the stable pipeline in Azure DevOps to monitor progress.
115
117
116
118
When the pipeline completes signing, it will pause for manual validation before publishing. Approve to publish to the VS Code Marketplace.
117
119
118
-
> ✋ **Confirm**: Has the tag been pushed and the pipeline started?
120
+
> ✋ **Confirm**: Has the tag been pushed and is the pipeline running?
0 commit comments