FIX: dotnet list succeeds with non-zero code

[justadreamer]

sometimes it succeeds with non zero exit code f.e.: https://github.com/51Degrees/ip-intelligence-dotnet-examples/actions/runs/19654042037/job/56323103125#step:4:603

[pi-alexander-popel]

Maybe we instead switch to https://github.com/51Degrees/common-ci/blob/main/dotnet/outdated.ps1? There seem to be two active PRs trying to plug weird holes in this script. I'd rather try replacing it with the dotnet-outdated tool.

[justadreamer]

Good idea, if that approach works and is cleaner - is there a way to test it prior to switching? F.e. running that script on some .NET repos like Pearl, cloud-dotnet, device-detection-dotnet, ip-intelligence-dotnet and see what updates will it generate and whether we'll see any bugs. so far the most bugging thing we encountered was the package downgrade due to the same dependency being directly and transitively referenced and being out of sync.

[pi-alexander-popel]

Not really. Until the switch is merged, the Package Update job won't pick it up. But fwiw, ip-intelligence-dotnet-examples already uses the script.

We don't have to run the entire pipeline, though. Just the Package Update. And if there are any bugs - doing a revert is easy enough, and nothing will get accidentally published this way.