Dependabot crashing when evaluating netstandard project NETSDK1005

[leotsarev]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

nuget

Package manager version

No response

Language version

No response

Manifest location and content before the Dependabot update

https://github.com/joinrpg/joinrpg-net/blob/2f618b66281f26329b551911205ddc7af3798df8/src/JoinRpg.XGameApi.Contract/JoinRpg.XGameApi.Contract.csproj#L1

dependabot.yml content

https://github.com/joinrpg/joinrpg-net/blob/2f618b66281f26329b551911205ddc7af3798df8/.github/dependabot.yml#L1

Updated dependency

No response

What you expected to see, versus what you actually saw

/usr/local/dotnet/current/sdk/9.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.targets(322,5): error NETSDK1005: Assets file '/home/dependabot/dependabot-updater/repo/src/JoinRpg.XGameApi.Contract/obj/project.assets.json' doesn't have a target for 'netstandard2.0'. Ensure that restore has run and that you have included 'netstandard2.0' in the TargetFrameworks for your project. [/home/dependabot/dependabot-updater/repo/src/JoinRpg.XGameApi.Contract/JoinRpg.XGameApi.Contract.csproj]

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

https://github.com/joinrpg/joinrpg-net/actions/runs/13376646657/job/37357221946

Smallest manifest that reproduces the issue

No response

[leotsarev]

The problem is that dependabot is calling dotnet build to determine dependencies and passing normalized TFM value netstandard2.0 (probably here

dependabot-core/nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs

Line 109 in 1213dc1

$"/p:TargetFramework={tfm}",

). And dotnet build is expecting exact value as it written in .csproj netstandard2.
I'm not sure that should be dependabot or SDK problem. SDK bug: dotnet/sdk#46947

[brettfo]

I haven't found any official documentation explicitly stating that netstandard2 isn't allowed, but in this list I only see netstandard2.0.

[leotsarev]

Fixing TFM didn't solve the issue, so I opened another ticket #11645

Talking about TFM, let's see what SDK team will say about this, but "netX" instead of "netX.0" always worked just fine. You just have to skip normalization on your side. Also, why you are passing /p:TargetFramework at all, if project has only one TargetFramework?