Skip to content

Conversation

@akoeplinger
Copy link
Member

This won't get updated anymore and we're already setting/overriding NETStandardLibraryRefPackageVersion in Versions.props

This won't get updated anymore and we're already setting/overriding NETStandardLibraryRefPackageVersion in Versions.props
Copilot AI review requested due to automatic review settings August 28, 2025 17:32
@github-actions
Copy link
Contributor

This PR is targeting main, which is now for .NET 11-facing work. If you intended to target .NET 10, either retarget this PR to release/10.0.1xx or make sure you backport the change to release/10.0.1xx after merging. See #50394 for more details.

Copy link
Contributor

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

This PR removes the NETStandard.Library.Ref dependency from version tracking files as it's no longer being updated and the version is already managed elsewhere in the build configuration.

  • Removes the NETStandard.Library.Ref dependency entry from Version.Details.xml
  • Removes the corresponding package version properties from Version.Details.props

Reviewed Changes

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

File Description
eng/Version.Details.xml Removes the NETStandard.Library.Ref dependency definition with its pinned version and repository information
eng/Version.Details.props Removes the NETStandardLibraryRefPackageVersion property and its corresponding version alias

<SystemTextJsonPackageVersion>10.0.0-rc.2.25416.109</SystemTextJsonPackageVersion>
<SystemWindowsExtensionsPackageVersion>10.0.0-rc.2.25416.109</SystemWindowsExtensionsPackageVersion>
<!-- dotnet/core-setup dependencies -->
<NETStandardLibraryRefPackageVersion>2.1.0</NETStandardLibraryRefPackageVersion>
Copy link
Member

Choose a reason for hiding this comment

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

Removing this would break the bundled versions generation I think. with the property empty, the build will pass, but it will write a blank and then later use that as a version number at compile time when building a project that targets 2.1

Copy link
Member Author

Choose a reason for hiding this comment

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

The property won't be empty since we set it here:

<NETStandardLibraryRefPackageVersion>2.1.0</NETStandardLibraryRefPackageVersion>

Copy link
Member

Choose a reason for hiding this comment

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

doh, I forgot we split out the props recently. nvm

@akoeplinger akoeplinger enabled auto-merge (squash) August 29, 2025 12:42
@akoeplinger akoeplinger merged commit f57e778 into main Aug 29, 2025
29 checks passed
@akoeplinger akoeplinger deleted the fix-ns2.1-ref branch August 29, 2025 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants