[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:

• MiYanni
• zivkan
• javiercn
• marcpopMSFT
• baronfel
• tmat
• dotnet-bot
• nohwnd
• SimonZhao888
• dotnet-maestro[bot]
• github-actions[bot]
• Youssef1313
• jjonescz
• dsplaisted

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.

[Youssef1313]

Nothing appears to be wrong with test templates to me.

See #51117 (comment)

We need to unblock this ASAP please

[Youssef1313]

This is something that might be broken for F# specifically. cc @zivkan as well because the failures appear to be related to _GetFrameworkAssemblyReferences which is defined by NuGet.

[MiYanni]

@Youssef1313 So, I've merged in the changes from #51020. There still seems to be test template problems. They say that the target Pack doesn't exist. 🤔

[Youssef1313]

@MiYanni There are similar failures in other tests as well so I doubt there is anything specific to test templates. All failures appear to be relates to NuGet in some way?

[Youssef1313]

@MiYanni @zivkan Any updates here please?

[MiYanni]

I've let the current @dotnet/domestic-cat be aware of this PR and the current problems.

[nagilson]

The pack issue is still present. @jkoritzinsky Is there any chance that the change you made to ProcessFrameworkReferences would impact _GetFrameworkAssemblyReferences? Adding both @zivkan @nkolev92 who may be able to add more context.

Project "C:\h\w\CD8D0A95\t\dotnetSdkTests\retlhfgc.ybw\Nuget_referen---546CE3DB\D_net45\D_net45.csproj" on node 1 (Pack target(s)).
C:\h\w\CD8D0A95\t\dotnetSdkTests\retlhfgc.ybw\Nuget_referen---546CE3DB\D_net45\D_net45.csproj : error MSB4057: The target "Pack" does not exist in the project.
Done Building Project "C:\h\w\CD8D0A95\t\dotnetSdkTests\retlhfgc.ybw\Nuget_referen---546CE3DB\D_net45\D_net45.csproj" (Pack target(s)) -- FAILED.

[baronfel]

@T-Gro was this Target something that you were seeing in your Type-Provider-packaging experiments recently?

[T-Gro]

@baronfel : The F# TP hook is adding a DependsOnTarget=_GetFrameworkAssemblyReferences into the list of TargetsForTfmSpecificContentInPackage. Which caused problems when _GetFrameworkAssemblyReferences would not otherwise be a natural part of the graph.

But I actually want to remove this dependency on _GetFrameworkAssemblyReferences , so that we would avoid the current failure that happens with pack --no-build.

[MiYanni]

What in the world is GitOps/YmlValidation?

[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}