-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[Release/6.0] Throw error if assembly version for ref pack assemblies doesnot match assembly version shipped in 6.0.0 #59535
Conversation
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsThis step is being added as an extra precaution to avoid incrementing the assembly versions for assemblies in the ref pack.
|
The failure be like this C:\git\runtime\eng\packaging.targets(261,5): error : AssemblyVersion should match last released assembly version 6.0.0.0
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:04.82
C:\git\runtime>dotnet build src\librarie |
Maybe include the project on the error for easier diagnostic? |
I think the error got trimmed. The eol contains the csproj name
|
Co-authored-by: Viktor Hofer <[email protected]>
cc @safern @ViktorHofer can you approve this one. |
/backport to main |
Started backporting to main: https://github.com/dotnet/runtime/actions/runs/1270845102 |
<Target Name="ValidateAssemblyVersionsInRefPack" | ||
Condition="$(_AssemblyInTargetingPack) == 'true' and '$(PreReleaseVersionLabel)' == 'servicing'" | ||
AfterTargets="CoreCompile" > | ||
<Error Condition="'$(AssemblyVersion)' != '$(LastReleasedStableAssemblyVersion)'" Text="AssemblyVersion should match last released assembly version $(LastReleasedStableAssemblyVersion)" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only runs for source assemblies. I assume that is desired?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes we never change ref assembly versions. They are pinned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assumed this code piece prevents someone from overriding the assembly version. If that's the case, what happens when someone overrides the assembly version in a library's Directory.Build.props file? Wouldn't the ref assembly be overridden then as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that _AssemblyInTargetingPack
was only set to true on ref assemblies as Targeting Pack
is the term for the ref pack and runtime pack for the package that carries the source assemblies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If that's the case, what happens when someone overrides the assembly version in a library's Directory.Build.props file?
i hope to catch these in the code review. This was basically to test the automatic update of assembly version that we do for the source assembies
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_AssemblyInTargetingPack
is true for assemblies that in ref pack but we version source assemblies using this property. ref assemblies are always pinned.
This step is being added as an extra precaution to avoid incrementing the assembly versions for assemblies in the ref pack.
We already automatically calculate it.