Skip to content

Switch stable pipeline trigger to release branches only #1003

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bschnurr merged 1 commit into from
Apr 23, 2026
+12 −9
Merged

Switch stable pipeline trigger to release branches only #1003

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions .github/agents/release.agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Start by reading `package.json` to determine the current version. Then confirm w

- **Even minor** = stable release (e.g. `2026.4.0` — *example*)
- **Odd minor** = pre-release / dev (e.g. `2026.3.0-dev`, `2026.5.0-dev` — *examples*)
- The stable release pipeline (`build/azure-devdiv-pipeline.stable.yml`) triggers on git tags matching `v*`
- The stable release pipeline (`build/azure-devdiv-pipeline.stable.yml`) triggers on pushes to `release/*` branches
- Tag format: `v<version>` (e.g. `v2026.4.0` — *example*)
- Release branch format: `release/<YYYY>.<EVEN_MINOR>` (e.g. `release/2026.4` — *example*)

Expand Down Expand Up @@ -66,7 +66,9 @@ git checkout main
git pull
git checkout -b release/2026.4
git push upstream release/2026.4
```
```

The stable release pipeline triggers automatically when the release branch is pushed to upstream.

> ✋ **Confirm**: Is the release branch pushed to upstream?

Expand Down Expand Up @@ -98,9 +100,9 @@ Goal: Keep `main` moving forward on an odd minor with `-dev` suffix.

---

### Phase 4 — Tag and trigger the pipeline
### Phase 4 — Tag the release

Goal: Push a tag from the release branch to trigger the stable pipeline.
Goal: Tag the release commit for GitHub release tracking.

Replace `release/2026.4` and `v2026.4.0` with the actual branch and version:
```
Expand All @@ -111,11 +113,11 @@ git tag v2026.4.0
git push upstream v2026.4.0
```

The pipeline triggers automatically on the new tag. Navigate to the stable pipeline in Azure DevOps to monitor the run.
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.

When the pipeline completes signing, it will pause for manual validation before publishing. Approve to publish to the VS Code Marketplace.

> ✋ **Confirm**: Has the tag been pushed and the pipeline started?
> ✋ **Confirm**: Has the tag been pushed and is the pipeline running?

---

Expand Down
7 changes: 4 additions & 3 deletions build/azure-devdiv-pipeline.stable.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
name: Publish Release
trigger:
tags:
include: ['v*']
trigger:
branches:
include:
- 'release/*'
pr: none

resources:
Expand Down
Loading