[DCR]: dotnet list package --outdated exit code

[cosminstirbu]

NuGet Product(s) Affected

dotnet.exe

Current Behavior

We'd like to check for outdated packages as part of our PR pipeline.

We would like to use dotnet list package --outdated, however there is no way to tell (without parsing the output), if there are any outdated packages.

Would it be possible to opt into returning a non-zero exit code if there are outdated packages, so we can then fail our pipeline / report on it?

Desired Behavior

Have an additional argument to dotnet list package --outdated to have it return a non-zero exit code if there are outdated packages (e.g., then number of outdated packages)

Additional Context

Original issue dotnet/sdk#25091

We're currently using dotnet-outdated/dotnet-outdated, however sometimes it is a hit or miss, because it fails to load the .sln.

[erdembayar]

Related issues:

• Set proper exit code on dotnet list package --vulnerable to enable usage in CI pipelines dotnet/sdk#16852
• dotnet audit & dotnet audit fix for NuGet packages. #11549 (comment)

Have an additional argument to dotnet list package --outdated to have it return a non-zero exit code if there are outdated packages (e.g., then number of outdated packages)

I like the idea of additional argument so it wouldn't break existing users.

[nkolev92]

Marking as duplicate of #11315.