-
Notifications
You must be signed in to change notification settings - Fork 446
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
Remove ExtraPackageVersionProps now that these version numbers should match without our intervention. #14769
Conversation
… match without our intervention.
1e81544
to
fecd739
Compare
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.
Approve - pending validation on Alpine.
I tested this on dotnet6 as I hadn't applied @tmds changes yet to that version, and it looks good. I'd have to fix my musl patches for dotnet7 to test there, but I don't expect there to be any difference. The backport process is clean as well. |
This looks like a proper fix to me (dotnet/source-build#3121). CI doesn't pass:
I think the sources that get built for the tarball may not actually contain the change introduced by this PR. |
Testing against NET 7, indeed this still causes issues for aspnetcore. Patch by @tmds works better. |
Due to how close to the wire we're getting I think this is going to have to go into servicing. Closing this in favor of #14549 and an eventual backport of it. |
I had removed the patch when I re-targeted main. What you have here should work. I think the Build_Tarball_x64 fails because it does a fresh check-out of In #14549 I had implemented it as a patch against |
Fixes dotnet/source-build#3071.
At one point the versions for MS.AspNetCore.App.Runtime and MS.AspNetCore.App.Runtime.platform didn't match and we needed this workaround. Now they are produced with the same unstable versions so we should be able to remove these lines.
@tmds and @ayakael, would you mind giving this a try in your environments?