[automated] Merge branch 'release/9.0.1xx' => 'release/9.0.2xx'

[github-actions]

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

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

• v-wuzhai
• joeloff
• github-actions[bot]
• marcpopMSFT
• dotnet-maestro[bot]
• jjonescz

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

# 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/sdk HEAD:merge/release/9.0.1xx-to-release/9.0.2xx

or if you are using SSH

git push git@github.com:dotnet/sdk HEAD:merge/release/9.0.1xx-to-release/9.0.2xx

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/9.0.1xx-to-release/9.0.2xx'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
The provided examples assume that the remote is named 'origin'. If you have a different remote name, please replace 'origin' with the name of your remote.

git fetch
git checkout -b merge/release/9.0.1xx-to-release/9.0.2xx origin/release/9.0.2xx
git pull /~https://github.com/dotnet/sdk merge/release/9.0.1xx-to-release/9.0.2xx
(make changes)
git commit -m "Updated PR with my changes"
git push /~https://github.com/dotnet/sdk HEAD:merge/release/9.0.1xx-to-release/9.0.2xx

or if you are using SSH

git fetch
git checkout -b merge/release/9.0.1xx-to-release/9.0.2xx origin/release/9.0.2xx
git pull git@github.com:dotnet/sdk merge/release/9.0.1xx-to-release/9.0.2xx
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/sdk HEAD:merge/release/9.0.1xx-to-release/9.0.2xx

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See /~https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

[nagilson]

@ellahathaway @mthalman Should the 9.0.102 SB stuff go into 9.0.200 or should we yoink it?
Need to finish this PR by the end of this week

[ellahathaway]

@ellahathaway @mthalman Should the 9.0.102 SB stuff go into 9.0.200 or should we yoink it? Need to finish this PR by the end of this week

Source-build builds and ships out of 1xx, so I don't think this stuff has to go into 2xx (unless 2xx somehow merges back into 1xx which I don't think is the case). That said, I'm not entirely understanding why you're asking. Is source-build blocking this PR?

[nagilson]

@ellahathaway @mthalman Should the 9.0.102 SB stuff go into 9.0.200 or should we yoink it? Need to finish this PR by the end of this week

Source-build builds and ships out of 1xx, so I don't think this stuff has to go into 2xx (unless 2xx somehow merges back into 1xx which I don't think is the case). That said, I'm not entirely understanding why you're asking. Is source-build blocking this PR?

So far no, I want to make sure that we are doing the right thing and not creating more churn for you/committing unnecessary stuff. Thank you for helping :)