(Copying from mail) Encountered by scenario testing on .NET Core 3.1.100-preview1-014066 SDK:

It looks like this string controls it:
@wli3 seems like a simple and small fix. Can you take care of that?
good catch
Verified this bug with .Net core 3.1.100-preview1-14455 from release branch, the issue has been fixed.
Result as below image:
@wli3 "dotnet new -l" using a 5.0 SDK welcomes me to still .NET Core 3.0 instead.

@wli3 seems like we missed this for 5, can you take care of it?
I think it did not flow to the branch. Now it is derived from the version below (SDK version)
Can you check where the code flow stands and push it through?! 馃槃