-
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] Add RID for Alpine 3.19 / 3.20 #99560
[release/6.0] Add RID for Alpine 3.19 / 3.20 #99560
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
0a62800
to
d7446ca
Compare
I've skipped main because we're not interested in this on main anymore, but tell me if I should up-port this somewhere. |
Unfortunately we might need to push this forward because of the back-compat switch. |
This PR doesn't apply to master since there are no more non-portable RIDs in RID graph. Do you mean I have to up-port to 7.0? |
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.
@ayakael I added the missing required Microsoft.NETCore.Platforms change.
I asked if we would still want a 7.0 equivalent RID update and it has been decided that we won't take one, as that branch only has one more month to live before EOL and it is currently only taking security fixes.
Agree we shouldn't need to apply to main. For the back-compat switch in 8.0+, the intent was that it would use to the 'frozen' non-portable RID graph - and we wouldn't update that non-portable RID graph (anything new should go through the new portable behaviour). |
@ayakael there is a build failure:
|
@elinor-fung I right, I see the lack of ppc64le + armv6 for the 6.0 release. Thanks for catching that! |
729e9bd
to
7d5b844
Compare
757ccc2
into
dotnet:release/6.0-staging
Adds RID for Alpine 3.19 and 3.20
Fixes #96155
Addresses dotnet/dotnet-docker#5243