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

[github-actions]

I detected changes in the release/10.0.1xx 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/10.0.1xx by the following committers:

• SimonZhao888
• dotnet-maestro[bot]
• marcpopMSFT
• github-actions[bot]
• jjonescz
• Youssef1313
• dotnet-bot
• elinor-fung

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/10.0.1xx
git pull --ff-only
git checkout main
git pull --ff-only
git merge --no-ff release/10.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/10.0.1xx-to-main

or if you are using SSH

git push [email protected]:dotnet/sdk HEAD:merge/release/10.0.1xx-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/10.0.1xx-to-main'. 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/10.0.1xx-to-main origin/main
git pull https://github.com/dotnet/sdk merge/release/10.0.1xx-to-main
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/sdk HEAD:merge/release/10.0.1xx-to-main

or if you are using SSH

git fetch
git checkout -b merge/release/10.0.1xx-to-main origin/main
git pull [email protected]:dotnet/sdk merge/release/10.0.1xx-to-main
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet/sdk HEAD:merge/release/10.0.1xx-to-main

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.

[SimonZhao888]

@marcpopMSFT, Referring to #50490 (comment) I'm not sure if we need to revert the changes to the Version.Details.xml file, as the version numbers for "Microsoft.DotNet.Arcade.Sdk" and "Microsoft.DotNet.Helix.Sdk" were modified in the global.json file.

sdk/global.json

Lines 24 to 25 in 7f7ee59

	"Microsoft.DotNet.Arcade.Sdk": "10.0.0-beta.25420.109",
	"Microsoft.DotNet.Helix.Sdk": "10.0.0-beta.25420.109",

[premun]

@SimonZhao888 @marcpopMSFT this is the kind of change that must not happen in these interbranch merges

[premun]

cc @mmitche

[SimonZhao888]

@SimonZhao888 @marcpopMSFT this is the kind of change that must not happen in these interbranch merges

So, for the internal PR like this, we need to temporarily close them until the backflow is resolved, right? Or do we just need to revert the changes related to the <Source> tag?

[premun]

It would technically be enough to revert the changes of the <Source> tag only.

We could maybe put a GitHub action in place to verify that Maestro PRs change this line?

[SimonZhao888]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).