[automated] Merge branch 'release/8.0.3xx' => 'main'

[dotnet-maestro-bot]

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

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

• marcpopMSFT
• baronfel
• invalid-email-address
• v-wuzhai
• dotnet-maestro[bot]
• dotnet-bot
• JL03-Yue
• Forgind
• dsplaisted
• nagilson
• jeffkl
• github-actions[bot]

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/8.0.3xx
git pull --ff-only
git checkout main
git pull --ff-only
git merge --no-ff release/8.0.3xx

# 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/8.0.3xx-to-main

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/sdk HEAD:merge/release/8.0.3xx-to-main

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/8.0.3xx-to-main'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

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

or if you are using SSH

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

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]

@Forgind @dsplaisted would you be able to review these changes? Thanks!

[nagilson]

I was surprised to see workload vm testing had not made it to main yet, not sure why this codeflow took so long to generate

[v-wuzhai]

Waiting for the code flow from #39573 to first be integrated into the main branch.

[MiYanni]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[marcpopMSFT]

C:\h\w\9FF208F4\t\dotnetSdkTests\ikyiv2ra.lys\ItCanBuildWit---0E92473C\MSBuildSdk\MSBuildSdk.csproj : error MSB4014: The build stopped unexpectedly because of an internal failure.
C:\h\w\9FF208F4\t\dotnetSdkTests\ikyiv2ra.lys\ItCanBuildWit---0E92473C\MSBuildSdk\MSBuildSdk.csproj : error MSB4014: Microsoft.Build.BackEnd.SdkResolution.SdkResolverException: The SDK resolver "Microsoft.DotNet.MSBuildSdkResolver" failed while attempting to resolve the SDK "Microsoft.Build.Artifacts". Exception: "System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.
C:\h\w\9FF208F4\t\dotnetSdkTests\ikyiv2ra.lys\ItCanBuildWit---0E92473C\MSBuildSdk\MSBuildSdk.csproj : error MSB4014: File name: 'Microsoft.Bcl.AsyncInterfaces, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'

[marcpopMSFT]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).