Stable branding for 18.9 release - #14218
Merged
Merged
Conversation
Phase 4.2 of the 18.9 release (dotnet#14213). Ran scripts/Stabilize-Release.ps1 on vs18.9: - Added <DotNetFinalVersionKind>release</DotNetFinalVersionKind> next to VersionPrefix (final-versioned builds; intentionally creates a forward-flow merge conflict). - Changed PreReleaseVersionLabel preview -> servicing. Phase 4.1 (public API promotion) is a no-op: the repo has no PublicAPI.Unshipped.txt entries to promote. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
JanProvaznik
temporarily deployed
to
copilot-pat-pool
June 30, 2026 12:31 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
JanProvaznik
temporarily deployed
to
copilot-pat-pool
June 30, 2026 12:32 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
JanProvaznik
temporarily deployed
to
copilot-pat-pool
June 30, 2026 12:32 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
70 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
Final-branding update for the vs18.9 release branch, aligning MSBuild’s versioning props with the release checklist process (stable/non-preview builds) and the repository’s documented release automation.
Changes:
- Add
<DotNetFinalVersionKind>release</DotNetFinalVersionKind>inline withVersionPrefix(intentionally to force forward-flow merge conflicts). - Change
PreReleaseVersionLabelfrompreviewtoservicing.
ViktorHofer
approved these changes
Jun 30, 2026
AlesProkop
approved these changes
Jun 30, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Phase 4.2/4.3 of the 18.9 release (#14213). Targets
vs18.9(the release branch), notmain.Final branding via
scripts/Stabilize-Release.ps1:<DotNetFinalVersionKind>release</DotNetFinalVersionKind>on theVersionPrefixline — switchesvs18.9to final-versioned (non-preview) builds. Kept next toVersionPrefixintentionally to create a forward-flow merge conflict (so this branding does not auto-flow intomain).PreReleaseVersionLabelpreview→servicing.Phase 4.1 (public API promotion) is a no-op — the repo has no
PublicAPI.Unshipped.txtentries to promote (consistent with the 18.8 final-branding PR #13883, which also only touchedeng/Versions.props).After merge:
vs18.9will fail for lack of OptProf data → cancel it and re-run manually with the OptProf override frommain's latest drop.vs18.9→ VSmain); final-branded bits must land in VSmainbefore the insiders snap (2026-07-02).