Skip to content

[vs18.3] Stabilize package versions#13233

Merged
JanProvaznik merged 2 commits into
dotnet:vs18.3from
JanProvaznik:fix/vs18.3-stable-versioning
Feb 10, 2026
Merged

[vs18.3] Stabilize package versions#13233
JanProvaznik merged 2 commits into
dotnet:vs18.3from
JanProvaznik:fix/vs18.3-stable-versioning

Conversation

@JanProvaznik

Copy link
Copy Markdown
Member

CI packages from vs18.3 are being produced with a -release.{commitid} pre-release suffix because DotNetFinalVersionKind was never set when the branch was stabilized.

This adds <DotNetFinalVersionKind>release</DotNetFinalVersionKind> to eng/Versions.props, matching the pattern used in vs17.14 and other servicing branches, so that packages are produced as stable 18.3.2 versions.

@JanProvaznik JanProvaznik requested a review from a team as a code owner February 10, 2026 13:16
Copilot AI review requested due to automatic review settings February 10, 2026 13:16
@JanProvaznik JanProvaznik force-pushed the fix/vs18.3-stable-versioning branch from 2699cdb to 589bc0f Compare February 10, 2026 13:17

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the vs18.3 branch versioning configuration so CI-produced packages are emitted as stable versions (e.g., 18.3.2) rather than using a -release.{commitid} prerelease suffix.

Changes:

  • Add <DotNetFinalVersionKind>release</DotNetFinalVersionKind> to eng/Versions.props to finalize package versioning as release.

Comment thread eng/Versions.props Outdated
@JanProvaznik JanProvaznik force-pushed the fix/vs18.3-stable-versioning branch from 589bc0f to 28d8af4 Compare February 10, 2026 13:19
@JanProvaznik JanProvaznik force-pushed the fix/vs18.3-stable-versioning branch from 28d8af4 to d3d4e83 Compare February 10, 2026 13:19
@JanProvaznik JanProvaznik merged commit 1a96e74 into dotnet:vs18.3 Feb 10, 2026
11 checks passed
This was referenced Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants