-
Notifications
You must be signed in to change notification settings - Fork 5.2k
fix stable pkg proj versioning support #58474
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
Conversation
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsFixes #57982
|
<PropertyGroup Condition="'$(PreReleaseVersionLabel)' == 'servicing'"> | ||
<IsShipping>false</IsShipping> | ||
</PropertyGroup> |
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.
Does that mean that none of these packages ship during servicing?
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.
they will get shipped internally
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.
Why do we change the definition of what's shipping publicly vs internally based on if the repo is in servicing mode?
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.
What packages are these specifically? IsShipping generally controls whether something goes to NuGet. Are they supposed to go to NuGet in non-servicing?
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.
Why do we change the definition of what's shipping publicly vs internally based on if the repo is in servicing mode?
basically following the same convention guidelines from the coreclr team as we did for 5.0.0
What packages are these specifically? IsShipping generally controls whether something goes to NuGet. Are they supposed to go to NuGet in non-servicing?
yes they are not supposed to go to nuget in non-servicing
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.
But they do go in rtm? What package set is this specifically?
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 they go to nuget in rtm, these https://github.com/dotnet/runtime/tree/main/src/coreclr/.nuget
Microsoft.ILVerification
Microsoft.NETCore.ILAsm
Microsoft.NETCore.ILDAsm
Microsoft.NETCore.TestHost
dotnet-ilverify
/backport to main |
Started backporting to main: https://github.com/dotnet/runtime/actions/runs/1199414650 |
@Anipik backporting to main failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: fix stable package proj versioning support
Using index info to reconstruct a base tree...
M src/coreclr/.nuget/Directory.Build.props
Falling back to patching base and 3-way merge...
Auto-merging src/coreclr/.nuget/Directory.Build.props
CONFLICT (content): Merge conflict in src/coreclr/.nuget/Directory.Build.props
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 fix stable package proj versioning support
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
Fixes #57982