-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[release/7.0-rc1] Roll forward to the latest 6.0.x builds #74288
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: @dotnet/area-infrastructure-libraries Issue Detailsnull
|
Tagging subscribers to this area: @directhex Issue DetailsStaging the updates to net7-workload-changes once it is complete in #74018
|
1151f8e
to
c7e8809
Compare
@dsplaisted this cross release version dependency is going to continue to be a problem |
@lewing , are you specifically talking about the 6.0.9 part of this PR or something else? This will end up being like the implicit version that the SDK uses. Once we are at GA, you can use msbuild logic so this doesn't have to be updated every month (though it will have to be updated any time the downlevel version doesn't release): https://github.com/dotnet/installer/blob/139aa5903a717425bd909a4cd2d5186eb99c2e2c/src/redist/targets/GenerateBundledVersions.targets#L29 |
All the impacted lanes are done here, merge at will. |
Staging the updates to net7-workload-changes once it is complete in #74018This bumps the 6.0.x builds to 6.0.9 which aren't in a feed CI can use, disables the tests that would fail as a result, and removes a workaround for the older manifests.