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

[github-actions]

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

• SimonZhao888
• dotnet-maestro[bot]
• marcpopMSFT
• github-actions[bot]
• tmat
• Youssef1313
• jjonescz
• nagilson
• dotnet-bot
• joeloff
• MiYanni
• baronfel
• dsplaisted
• jkoritzinsky
• elinor-fung
• Copilot
• invalid-email-address
• mthalman
• 333fred
• nohwnd
• javiercn
• MichaelSimons
• zivkan

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.2xx
git pull --ff-only
git checkout main
git pull --ff-only
git merge --no-ff release/10.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/sdk HEAD:merge/release/10.0.2xx-to-main

or if you are using SSH

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

or if you are using SSH

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

[MiYanni]

@marcpopMSFT That wasn't the right course of action IMO. I've been awaiting that 1xx PR to flow into main.

Namely, this commit in here: cec531e (#50946)
Which came from this PR: #51020
Which is still blocking my PR here: #50895

The reason I went this route is because:

1. The change was made to 1xx which should flow to main automatically.
2. Auto-backport to main of the Run test template tests with Arcade #51020 PR failed.
3. That change fixed a failure in the 1xx to main PR.

[marcpopMSFT]

but the correct flow is 1xx->2xx->main now. If the 1xx to main was close (which it didn't look like it), we could continue investing there but what's the difference between than and flowing through 2xx?

[MiYanni]

@marcpopMSFT Because that PR from 1xx to main was opened Sept 20th and has had investigation/interaction around the issues. Waiting longer may cause more issues than less. Personally, I just didn't want that branch merge to be delayed even longer. It might cause a snowball effect of issues (where it gets even harder to diagnose and fix).

[Youssef1313]

@marcpopMSFT @MiYanni @baronfel Any updates here please?

[joeloff]

@Youssef1313 did the _GetFrameworkAssemblyReferences change make it into main?

[joeloff]

@dotnet/nuget-team Most of the failing tests seems to be hitting issues around _GetFrameworkAssemblyReferences. AFAIK, that target comes from NuGet. Anything obvious that comes to mind we might have missed in our codeflows?

[dotnet-policy-service]

1 file(s) have code issues.

File	Issues
.github/policies/resourceManagement.yml	Exception during deserialization. Failed to create an instance of type 'GitOps.PullRequestIssueManagement.Core.Primitives.Data.Frequencies.SearchFrequency'.. Cannot dynamically create an instance of type 'GitOps.PullRequestIssueManagement.Core.Primitives.Data.Frequencies.SearchFrequency'. Reason: Cannot create an abstract class.

_{Total execution time: 0.00 seconds}