You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running dotnet outdated gives the following output:
❯ dotnet outdated
Discovering projects...
Analyzing project(s)...
Analyzing dependencies...
» _scratch
[net6.0]
System.Text.Json 6.0.0 -> 10.0.0
Version color legend:
<red> : Major version update or pre-release version. Possible breaking changes.
<yellow>: Minor version update. Backwards-compatible features added.
<green> : Patch version update. Backwards-compatible bug fixes.
You can upgrade packages to the latest version by passing the -u or -u:prompt option.
Elapsed: 00:00:02.8920607
However, after the target framework is updated to net10.0, the upgrade is no longer detected:
❯ dotnet outdated
Discovering projects...
Analyzing project(s)...
Analyzing dependencies...
No outdated dependencies were detected
Elapsed: 00:00:01.1248270
My guess is that this is related to NuGet package pruning and NU1510. While the reference is indeed redundant, it still makes sense to detect it is outdated.
Consider the following project:
Running
dotnet outdatedgives the following output:However, after the target framework is updated to
net10.0, the upgrade is no longer detected:<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <OutputType>Exe</OutputType> - <TargetFramework>net6.0</TargetFramework> + <TargetFramework>net10.0</TargetFramework> </PropertyGroup> <ItemGroup> <PackageReference Include="System.Text.Json" Version="6.0.0" /> </ItemGroup> </Project>My guess is that this is related to NuGet package pruning and NU1510. While the reference is indeed redundant, it still makes sense to detect it is outdated.