[automated] Merge branch 'release/5.0.2xx' => 'master'

[dotnet-maestro-bot]

I detected changes in the release/5.0.2xx branch which have not been merged yet to master. I'm a robot and am configured to help you automatically keep master up to date, so I've opened this PR.

This PR merges commits made on release/5.0.2xx by the following committers:

• dotnet-maestro[bot]
• dsplaisted
• AntonLapounov
• sfoslund
• mavasani
• wli3
• mmitche
• nkolev92
• v-wuzhai
• marcpopMSFT
• baronfel
• rainersigwald

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout release/5.0.2xx
git pull --ff-only
git checkout master
git pull --ff-only
git merge --no-ff release/5.0.2xx

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/sdk HEAD:merge/release/5.0.2xx-to-master

or if you are using SSH

git push [email protected]:dotnet-maestro-bot/sdk HEAD:merge/release/5.0.2xx-to-master

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/5.0.2xx-to-master'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/5.0.2xx-to-master master
git pull https://github.com/dotnet-maestro-bot/sdk merge/release/5.0.2xx-to-master
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/sdk HEAD:merge/release/5.0.2xx-to-master

or if you are using SSH

git checkout -b merge/release/5.0.2xx-to-master master
git pull [email protected]:dotnet-maestro-bot/sdk merge/release/5.0.2xx-to-master
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet-maestro-bot/sdk HEAD:merge/release/5.0.2xx-to-master

Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

[v-wuzhai]

@wli3 @sfoslund I resolved the conflicts, do we need to merge it?

[sfoslund]

Found .NET SDK, but did not find dotnet.dll

Yes, we will want to merge this once we resolve the test failures.

It looks like this line shows up in the merge and is causing the failures, is it needed @wli3?
<OverlaySdkFilesFromStage0 Include="$(_DotNetHiveRoot)/sdk/$(Stage0SdkVersion)/NETCoreSdkRuntimeIdentifierChain.txt" />

[wli3]

<OverlaySdkFilesFromStage0 Include="$(_DotNetHiveRoot)/sdk/$(Stage0SdkVersion)/NETCoreSdkRuntimeIdentifierChain.txt" />

is needed in master. @dsplaisted added the feature so that we can use the RID chain (generate in build time of dotnet/installer) to find the most fit pack instead of a hard coded list.

[dsplaisted]

Looks like we don't have test coverage of the NETCoreSdkRuntimeIdentifierChain.txt file. I added a note to add that as part of #14841.

Ideally we would merge 5.0.2xx to master for dotnet/installer, then update this PR to use the updated stage 0, and include the file in the list to copy from Stage 0.

[dsplaisted]

Here's the merge to master for dotnet/installer: dotnet/installer#9203