dotnet list package --outdated exit code

[cosminstirbu]

Hello,

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?

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

Thank you,
Cosmin

[KalleOlaviNiemitalo]

This is somewhat related to NuGet/Home#8087 (exit code for vulnerable packages) and NuGet/Home#7752 (machine-readable dotnet list package so you'd at least be able to parse it more easily).

[ghost]

Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue!

If you believe this issue was closed out of error, please comment to let us know.

Happy Coding!