Merged
Conversation
Add DotNetFinalVersionKind=release and change PreReleaseVersionLabel to servicing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
53 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
Finalizes MSBuild 18.6 release-branch branding by switching the versioning knobs used by Arcade/VS insertion to produce release (non-prerelease-suffixed) outputs and align subsequent servicing builds.
Changes:
- Add
<DotNetFinalVersionKind>release</DotNetFinalVersionKind>alongsideVersionPrefix(intentionally inline to force forward-flow conflicts). - Change
PreReleaseVersionLabelfrompreviewtoservicing.
ViktorHofer
approved these changes
Mar 31, 2026
JanProvaznik
approved these changes
Mar 31, 2026
This was referenced Apr 15, 2026
JanProvaznik
pushed a commit
that referenced
this pull request
Apr 30, 2026
Phase 4 of the [18.7 release checklist](#13639): final branding for the 18.7.0 release. ### Changes (generated by `scripts/Stabilize-Release.ps1`) - Add `<DotNetFinalVersionKind>release</DotNetFinalVersionKind>` on the `VersionPrefix` line (kept inline to create a conflict in forward-flow per release docs) - Change `PreReleaseVersionLabel` from `preview` to `servicing` ### Notes - **Phase 4.1 (PublicAPI promotion)**: no-op — there are no non-empty `PublicAPI.Unshipped.txt` entries on `vs18.7`. - Same shape as 18.6 final branding PR #13473.⚠️ **Time-sensitive**: VS snaps `main` → `rel/insiders` on **2026-05-01**. Final-branded bits need to be in VS `main` before the snap. Tracks #13639. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Release 18.6 — Phase 4: Final Branding
Tracking issue: #13468
Changes
Generated by \scripts/Stabilize-Release.ps1.
Next steps after merge