Notification for subscribed users from https://github.com/dotnet/templating:

@dotnet/templating-engine-maintainers

Action requested: Please take a look at this failing automated dependency-flow pull request's checks; failures may be related to changes which originated in your repo.

• This pull request contains changes from your source repo (https://github.com/dotnet/templating) and seems to have failed checks in this PR. Please take a peek at the failures and comment if they seem relevant to your changes.
• If you're being tagged in this comment it is due to an entry in the related Maestro Subscription of the Build Asset Registry. If you feel this entry has added your GitHub login or your GitHub team in error, please update the subscription to reflect this.
• For more details, please read the Arcade Darc documentation

@MiYanni, @marcpopMSFT, most GivenThatWeWantToBuild test cases fail because of the following reasons:

Microsoft.NET.TargetFrameworkInference.targets(187,5): warning NETSDK1215: Targeting .NET Standard prior to 2.0 is no longer recommended. See https://aka.ms/dotnet/dotnet-standard-guidance for more details. [Q:\SDK\artifacts\tmp\Debug\It_builds_the---209C4D06\TestLibrary\TestLibrary.fsproj]
Microsoft.NET.TargetFrameworkInference.targets(187,5): warning NETSDK1215: Targeting .NET Standard prior to 2.0 is no longer recommended. See https://aka.ms/dotnet/dotnet-standard-guidance for more details. [Q:\SDK\artifacts\tmp\Debug\It_builds_the---209C4D06\TestLibrary\TestLibrary.fsproj]
error NU1202: Package System.ValueTuple 4.6.1 is not compatible with netstandard1.6 (.NETStandard,Version=v1.6). Package System.ValueTuple 4.6.1 supports:
error NU1202:   - net462 (.NETFramework,Version=v4.6.2)
error NU1202:   - net47 (.NETFramework,Version=v4.7)
error NU1202:   - net471 (.NETFramework,Version=v4.7.1)
error NU1202:   - netcoreapp2.0 (.NETCoreApp,Version=v2.0)
error NU1202:   - netstandard2.0 (.NETStandard,Version=v2.0)

When the lock is released, I want to bring 2a856e5 and 48a2a31 to release/9.0.1xx branch to fix the test failure. What do you think about this?

The same issue in PR 49535.

So you want to back port the test change that updates a bunch of tests to target netstandard2.0 instead of netstandard1.5? That seems like a reasonable thing to do. You could cherry pick that change into this branch and see if it passes checks fwiw. I guess it's possible targeting an older netstandard could break but we recommend 2.0 or 2.1 so I'm not too worried about the lost coverage.