Resolve .NET versions using productVersions.txt assets instead of productCommit asset
#6732
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.
Now that the public daily build of .NET has a stable version number, The SDK's productCommit-linux-x64.txt asset no longer contains enough information to update dependencies with. It contains stable versions now, e.g.
10.0.0/10.0.100.Instead of updating versions using the contents of that file, we can resolve the versions of the individual SDK/runtime/aspnet components using their respective productVersion.txt files. We don't even have to read the contents of the files, we can just use the version directly from the BAR assets metadata.
This change was used to create this commit in #6727: dotnet-docker-bot@89487f4.