From 1f3add1c1cb52be6f9a097226d382b355f82467e Mon Sep 17 00:00:00 2001
From: YuliiaKovalova <95473390+YuliiaKovalova@users.noreply.github.com>
Date: Wed, 19 Nov 2025 16:38:34 +0100
Subject: [PATCH 1/3] Revise release steps for MSBuildLocator

Updated the release process for MSBuildLocator to reflect changes in the pipeline build and release steps.
---
 Releasing_MSBuildLocator.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Releasing_MSBuildLocator.md b/Releasing_MSBuildLocator.md
index 4270b464..dc182b51 100644
--- a/Releasing_MSBuildLocator.md
+++ b/Releasing_MSBuildLocator.md
@@ -5,10 +5,10 @@ These instructions can only be followed by Microsoft-internal MSBuild maintainer
 1. Create a PR in https://github.com/microsoft/MSBuildLocator
 2. Have it reviewed.
 3. Once approved, merge it.
-4. It will automatically start a pipeline build [here](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11881).
-5. Once it succeeds, proceed to [our release page](https://dev.azure.com/devdiv/DevDiv/_release?_a=releases&view=mine&definitionId=408) and create a release (top-right). Specify the build that succeeded.
-6. At some point, it will stop to request permission to continue. If you want to publish to NuGet, do so, clicking Approve. It will make a little more progress and push to NuGet! It will then give you the option to "resume" (or cancel) twice. Do so.
-
+4. Startt a pipeline build [here](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11881) for the commited changes.
+5. Once it succeeds, proceed to [our release pipeline](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=27492) and queue release. Specify the build that succeeded.
+6. On Public NuGet release stage it will stop to request permission to continue. If you want to publish to NuGet, do so, clicking Approve.
+   
 ### Releasing a non-preview version of MSBuildLocator
 
 The above steps will push a package to NuGet.org, but it is a preview version. To make a final release branded version, merge the latest changes into a release branch like `release/1.5`. Follow the steps as above, and it will publish a release package to NuGet.org.

From d90e3a5af852aab596759f9f9367136e7d2e52cb Mon Sep 17 00:00:00 2001
From: YuliiaKovalova <95473390+YuliiaKovalova@users.noreply.github.com>
Date: Wed, 19 Nov 2025 16:39:00 +0100
Subject: [PATCH 2/3] Remove GitHub release job from pipeline

---
 release-pipeline.yml | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/release-pipeline.yml b/release-pipeline.yml
index 33a74788..f519072a 100644
--- a/release-pipeline.yml
+++ b/release-pipeline.yml
@@ -79,14 +79,3 @@ stages:
           https://microsoft.sharepoint.com/teams/toolsforeng/_layouts/OneNote.aspx?id=%2Fteams%2Ftoolsforeng%2FOne%20Note%2FToolsForSoftwareEngineers&wd=target%28Build%20Tools%2FMSBuild%2FGitHub.one%7CFF6DC598-65EC-43D5-AB29-DB38FEB82BC8%2FMyGet%20Feed%7CFAFC6258-899D-48D4-8DB4-892396202C9C%2F%29
           onenote:https://microsoft.sharepoint.com/teams/toolsforeng/One%20Note/ToolsForSoftwareEngineers/Build%20Tools/MSBuild/GitHub.one#MyGet%20Feed&section-id={FF6DC598-65EC-43D5-AB29-DB38FEB82BC8}&page-id={FAFC6258-89
         onTimeout: 'reject'
-
-  - job: GitHubRelease
-    displayName: 'GitHub release'
-    dependsOn: PublicNuGetRelease
-    pool: server
-    steps:
-    - task: ManualValidation@0
-      displayName: 'Create GitHub release'
-      inputs:
-        instructions: 'Create the GitHub release manually'
-        onTimeout: 'reject'

From 68fb12e746f43cedf98e94c2e3110fef73d7db40 Mon Sep 17 00:00:00 2001
From: YuliiaKovalova <95473390+YuliiaKovalova@users.noreply.github.com>
Date: Wed, 19 Nov 2025 16:39:37 +0100
Subject: [PATCH 3/3] Fix typo in pipeline build instruction

---
 Releasing_MSBuildLocator.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Releasing_MSBuildLocator.md b/Releasing_MSBuildLocator.md
index dc182b51..0c83875b 100644
--- a/Releasing_MSBuildLocator.md
+++ b/Releasing_MSBuildLocator.md
@@ -5,7 +5,7 @@ These instructions can only be followed by Microsoft-internal MSBuild maintainer
 1. Create a PR in https://github.com/microsoft/MSBuildLocator
 2. Have it reviewed.
 3. Once approved, merge it.
-4. Startt a pipeline build [here](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11881) for the commited changes.
+4. Start a pipeline build [here](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11881) for the commited changes.
 5. Once it succeeds, proceed to [our release pipeline](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=27492) and queue release. Specify the build that succeeded.
 6. On Public NuGet release stage it will stop to request permission to continue. If you want to publish to NuGet, do so, clicking Approve.