Work around Android CI workflow errors #6436
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
global.json
on latest GitHub Action windows runners dotnet/sdk#45204Something extremely funny is happening straight from Windows Runner Image 20241113.3.0, where installing workloads without specifying a version installs ones from .NET 7(????)
This part should be enough to show how messed up the situation seems to be. The command execution shows that the used .NET SDK is correct, but the installed workloads point to .NET 7 versions. Moreover, the workload install output shows that it is installing both .NET 6 and .NET 7 versions of the workflow, which is just ??????
Fortunately, with the assumption that a workload manifest is published for every .NET SDK release, the pushed workaround which explicitly specifies the .NET SDK version we're using should hold enough until we move to .NET 9