Skip to content

Do not use StabilizePackageVersion in project infra #116152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 1, 2025

Conversation

mmitche
Copy link
Member

@mmitche mmitche commented May 30, 2025

This property was originally just meant to be a repo global input, which was then used to set DotNetFinalVersionKind in Versions.props. That is then used in arcade to determine the package version. Where we are using StabilizePackageVersion, use DotNetFinalVersionKind.

This property was originally just meant to be a repo global input, which was then used to set DotNetFinalVersionKind in Versions.props. That is then used in arcade to determine the package version.
Where we are using StabilizePackageVersion, use DotNetFinalVersionKind.
@Copilot Copilot AI review requested due to automatic review settings May 30, 2025 16:35
@mmitche mmitche requested a review from jkoritzinsky May 30, 2025 16:35
@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label May 30, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

The PR replaces uses of the StabilizePackageVersion MSBuild property with DotNetFinalVersionKind across project files to centralize version stabilization logic. It also updates test assertions to accommodate the new version format.

  • Swap MSBuild conditions from StabilizePackageVersion to DotNetFinalVersionKind in multiple .csproj and .targets files
  • Adapt the framework description test to allow “-preview.*.final” suffixes
  • Ensure consistency in version-related DefineConstants flags

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file
File Description
src/mono/wasm/Wasm.Build.Tests/Wasm.Build.Tests.csproj Update runtime pack version condition to use DotNetFinalVersionKind
src/mono/wasi/Wasi.Build.Tests/Wasi.Build.Tests.csproj Same update for Wasi build tests
src/mono/nuget/Microsoft.NET.Runtime.WorkloadTesting.Internal/Sdk/WorkloadTesting.Core.targets Use DotNetFinalVersionKind for workload manifest version
src/mono/nuget/Directory.Build.targets Update StableVersion condition to DotNetFinalVersionKind
src/libraries/System.Runtime/tests/System.Runtime.InteropServices.RuntimeInformation.Tests/System.Runtime.InteropServices.RuntimeInformation.Tests.csproj Switch DefineConstants check to DotNetFinalVersionKind
src/libraries/System.Runtime/tests/System.Runtime.InteropServices.RuntimeInformation.Tests/DescriptionNameTests.cs Broaden stabilized version assertion to include “final” suffix
src/libraries/System.Private.CoreLib/gen/System.Private.CoreLib.Generators.csproj Switch DefineConstants to DotNetFinalVersionKind
src/installer/tests/Assets/Projects/Directory.Build.targets Update _UpdatedVersion condition
src/coreclr/.nuget/Directory.Build.targets Update StableVersion condition
Comments suppressed due to low confidence (1)

src/mono/wasi/Wasi.Build.Tests/Wasi.Build.Tests.csproj:99

  • The comment references Wasm.Build.Tests but this is the Wasi.Build.Tests project file. Please update it to correctly refer to Wasi.Build.Tests.
<!-- Wasm.Build.Tests are not a shipping project, PackageVersion will have a version suffix even for release branch, where actual runtime pack version doesn't have version suffix. Copy & paste to Wasm.Build.Tests -->

Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@mmitche mmitche merged commit ab29e9e into dotnet:main Jun 1, 2025
159 of 161 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants