Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions eng/Versions.props
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,8 @@
<VersionFeature60>36</VersionFeature60>
<VersionFeature70>20</VersionFeature70>
<!-- This version should be N-1 (ie the currently released version) in the preview branch but N-2 in main so that workloads stay behind the unreleased version -->
<VersionFeature80>23</VersionFeature80>
<VersionFeature90>12</VersionFeature90>
<VersionFeature80>$([MSBuild]::Add($(VersionFeature), 25))</VersionFeature80>
<VersionFeature90>$([MSBuild]::Add($(VersionFeature), 14))</VersionFeature90>
Comment on lines 39 to +41
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

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

Deriving VersionFeature80/90 from $(VersionFeature) means a PR that only bumps will now also implicitly change the net8/net9 runtime/targeting pack versions at build time. This can break automation/policy that treats “only changed in eng/Versions.props” as a low-impact change (e.g., .github/workflows/remove-lockdown-label.yml checks the diff for only). Consider keeping VersionFeature80/90 explicit, or updating the automation/policy to account for these derived properties so branch-lockdown behavior stays correct.

Copilot uses AI. Check for mistakes.
<!-- Should be kept in sync with VersionFeature70. It should match the version of Microsoft.NET.ILLink.Tasks
referenced by the same 7.0 SDK that references the 7.0.VersionFeature70 runtime pack. -->
<_NET70ILLinkPackVersion>7.0.100-1.23211.1</_NET70ILLinkPackVersion>
Expand Down