MSBuild Release Checklist 18.7

[SimaTian]

Inputs

Placeholder	Description	Value
PREVIOUS_RELEASE_VERSION	Version being replaced as latest	18.6
THIS_RELEASE_VERSION	Version being released now	18.7
THIS_RELEASE_EXACT_VERSION	Full VersionPrefix on release branch after final branding	18.7.0
NEXT_VERSION	Version that main will be bumped to	18.8

Derived values:

• Release branch: vs18.7
• DARC channel: VS 18.7
• Next DARC channel: VS 18.8
• VS insertion target: VS main (VS snaps main → insiders → stable on its own schedule)

Phase 0: Instantiate Release

Trigger: User decides to start a release. Do this first.

• Validate inputs:
  • Confirm eng/Versions.props on main has VersionPrefix = 18.7.0
  • Confirm branch vs18.7 does not already exist
  • Confirm DARC channel VS 18.7 exists (ID: 10189)
• Create this tracking issue in dotnet/msbuild with all placeholders replaced
• Record all tracking URLs in the table below as phases are completed:

Artifact	URL
Next-version branding PR
VisualStudio.ChannelName PR
Phase 1 DARC config PR	https://dev.azure.com/dnceng/internal/_git/maestro-configuration/pullrequest/60575
Phase 3 DARC config PR
Final branding PR
VS insertion PR
Channel promotion PR

---

Phase 1: Branch & Prepare

Trigger: 2026-05-01 reached (VS snaps main → rel/insiders for 18.7; per Dev18.7 Schedule).

Steps are sequential — complete in order.

• 1.1 Create branch vs18.7 from HEAD of main:
  git push upstream HEAD:refs/heads/vs18.7
  • If branched too early (main has commits that shouldn't be in the release): fast-forward the branch to the correct commit (the one currently inserted into VS main):
    git push upstream :refs/heads/vs18.7
• 1.2 DARC configuration — batch all channel/mapping changes into one PR on the maestro-configuration repo.
  Use --configuration-branch release/msbuild-18.7 on every command and --no-pr on all but the last:
  • 1.2a Ensure branch-to-channel association exists:
    First check: darc get-default-channels --channel "VS 18.7" --branch vs18.7 --source-repo https://github.com/dotnet/msbuild
    If No matching channels were found.:
    darc add-default-channel --channel "VS 18.7" --branch vs18.7 --repo https://github.com/dotnet/msbuild --configuration-branch release/msbuild-18.7 --no-pr
  • 1.2b Create DARC channel for next release:
    darc add-channel --name "VS 18.8" --configuration-branch release/msbuild-18.7 --no-pr
    (Channel VS 18.8 already exists — ID 10188, so this is a no-op.)
  • 1.2c Pre-create default channel mapping for the next release branch (last command — omit --no-pr to create the PR):
    darc add-default-channel --channel "VS 18.8" --branch vs18.8 --repo https://github.com/dotnet/msbuild --configuration-branch release/msbuild-18.7
  • 1.2d Get the maestro-configuration PR reviewed and merged
  • 1.2e Ping internal "First Responders" Teams channel to get the new VS 18.8 channel available as a promotion target
    • Not needed — VS 18.7/18.8/18.9/18.10 publishing entries were added to arcade in dotnet/arcade@e385506c on 2026-03-21 (PR arcade#16617). Maestro/BAR accepts the channel — verified by PR #60575 and darc add-default-channel "VS 18.8".
    • Follow-up: pending arcade dep-flow PR [main] Update dependencies from dotnet/arcade #13434 (DIRTY since 2026-03-23) needs rebase+merge so msbuild's main arcade pin picks up the new publishing constants.
• 1.3 Update .config/git-merge-flow-config.jsonc:
  Insert vs18.7 as the last entry before main in the merge chain. Add a comment noting the VS/SDK version context.

---

Phase 2: Bump Main & Update Pipelines

Trigger: vs18.7 branch exists (Phase 1.1 done). Previous release is in insiders stage.

Create one PR in main containing all of the following changes:

• 2.1 eng/Versions.props: Update VersionPrefix to 18.8.0
• 2.2 eng/Versions.props: Update PackageValidationBaselineVersion to 18.7.0-preview-26229-01 (matches the 18.7 preview just inserted into VS main).
• 2.3 If needed, update CompatibilitySuppressions.xml files. Run:
  dotnet pack MSBuild.Dev.slnf /p:ApiCompatGenerateSuppressionFile=true
  See API compat documentation for details.
  • Only required if ApiCompat fails CI on PR Bump main to 18.8.0 after vs18.7 snap #13657.
• 2.4 azure-pipelines/vs-insertion.yml: no AutoInsertTargetBranch field on the current version — no change needed.
• 2.5 azure-pipelines/vs-insertion-experimental.yml: already lists main/rel/insiders/rel/stable — no change needed.
• 2.6 Merge branding PR Bump main to 18.8.0 after vs18.7 snap #13657

---

Phase 3: DARC Subscription Updates

Trigger: Phase 2 branding PR merged (main now has 18.8 version).

First, gather information (read-only queries — no PR needed):

• 3.1 Find the SDK main subscription ID to update:
  darc get-subscriptions --exact --source-repo https://github.com/dotnet/msbuild --channel "VS 18.7"
  Note the subscription ID for the SDK main branch entry.
• 3.2 Verify release branch channel association:
  darc get-default-channels --source-repo https://github.com/dotnet/msbuild --branch vs18.7
  Note whether the association exists (needed for step 3.3d).

Then, batch all write operations into one PR on the maestro-configuration repo.
Use --configuration-branch release/msbuild-18.7-main-bump and --no-pr on all but the last command:

• 3.3 DARC channel/subscription updates:
  • 3.3a Remove main → old channel mapping:
    darc delete-default-channel --repo https://github.com/dotnet/msbuild --branch main --channel "VS 18.7" --configuration-branch release/msbuild-18.7-main-bump --no-pr
  • 3.3b Associate main with next channel:
    darc add-default-channel --channel "VS 18.8" --branch main --repo https://github.com/dotnet/msbuild --configuration-branch release/msbuild-18.7-main-bump --no-pr
  • 3.3c Update SDK main subscription to new channel:
    darc update-subscription --id <SUBSCRIPTION_ID_FROM_3.1> --channel "VS 18.8" --configuration-branch release/msbuild-18.7-main-bump --no-pr
  • 3.3d If release branch association was missing in 3.2, add it:
    darc add-default-channel --channel "VS 18.7" --branch vs18.7 --repo https://github.com/dotnet/msbuild --configuration-branch release/msbuild-18.7-main-bump --no-pr
  • 3.3e If any subscriptions need fixing (from 3.4–3.6 below), include them here with --no-pr.
  • 3.3f Create the PR — re-run step 3.3b (or whichever was the last write command executed) without --no-pr to open the PR on the configuration branch.
  • 3.3g Get the maestro-configuration PR reviewed and merged

Verifications (parallel — read-only, no ordering dependency):

• 3.4 Verify Arcade subscription:
  darc get-subscriptions --exact --target-repo https://github.com/dotnet/msbuild --source-repo https://github.com/dotnet/arcade
• 3.5 Verify NuGet client subscription:
  darc get-subscriptions --exact --target-repo https://github.com/dotnet/msbuild --source-repo https://github.com/nuget/nuget.client
• 3.6 Verify Roslyn subscription:
  darc get-subscriptions --exact --target-repo https://github.com/dotnet/msbuild --source-repo https://github.com/dotnet/roslyn
• 3.7 Confirm Roslyn and NuGet subscriptions are disabled (Enabled: False)
• 3.8 Fix any missing or misconfigured subscriptions

---

Phase 4: Final Branding & VS Insertion

Trigger: 7 calendar days before 2026-05-01 (i.e., ~2026-04-24).
Precondition: Phases 1–3 complete. Preview builds from vs18.7 have been inserting into VS main since Phase 2.
Goal: Final-brand the release branch and get the final-branded bits inserted into VS main before VS snaps to rel/insiders.

Steps are sequential.

• 4.1 Promote public API on vs18.7 branch:
  No-op — no non-empty PublicAPI.Unshipped.txt entries on vs18.7.
• 4.2 Run scripts/Stabilize-Release.ps1 on vs18.7 branch:
  Applied via PR Final branding for 18.7 release #13658.
• 4.3 Create and merge final branding PR to vs18.7 (PR Final branding for 18.7 release #13658)
• 4.4 Bootstrap OptProf for vs18.7:
  • Run the official build for vs18.7 with Optional OptProfDrop Override set to main's latest OptProf drop path, or set SkipApplyOptimizationData to true.
  • Verify that the OptProf data collection pipeline triggers for vs18.7.
  • Run the official build for vs18.7 with no overrides.
• 4.5 Get M2 or QB approval as necessary per the VS schedule
• 4.6 Babysit the VS insertion PR from vs18.7 into VS main. Final-branded bits must be in VS main before 2026-05-01.
• 4.7 (After insiders snap on 2026-05-01, if needed) Retarget AutoInsertTargetBranch for vs18.7 from VS main → rel/insiders.
• 4.8 (After stable snap on 2026-05-27, if needed) Retarget AutoInsertTargetBranch for vs18.7 → rel/stable.

---

Phase 5: Post-GA

Trigger: 2026-06-09 has passed and VS release (18.7.0 Feature Update) has shipped.

• 5.1 Push packages to nuget.org (contact dnceng). Packages:
  • Microsoft.Build.Utilities.Core.18.7.0.nupkg
  • Microsoft.Build.18.7.0.nupkg
  • Microsoft.Build.Framework.18.7.0.nupkg
  • Microsoft.Build.Runtime.18.7.0.nupkg
  • Microsoft.Build.Tasks.Core.18.7.0.nupkg
  • Microsoft.NET.StringTools.18.7.0.nupkg
  • Microsoft.Build.Templates.18.7.0.nupkg
• 5.2 Publish docs at https://aka.ms/publishondocs
• 5.3 Create GitHub release:

  git checkout <COMMIT>
  git tag v18.7.0
  git push upstream v18.7.0
  

  Create release at https://github.com/dotnet/msbuild/releases/new
• 5.4 Update BootstrapSdkVersion in eng/Versions.props if a fresh SDK was released.
• 5.5 Extend OptProf data expiration for vs18.7 branch if the release is LTSC.
• 5.6 Verify main subscriptions point to VS 18.8 channel:
  darc get-subscriptions --exact --target-repo https://github.com/dotnet/msbuild --target-branch main
• 5.7 Review this tracking issue for any process deviations.