Leszek 'skolima' Ciesielski

We're not planning on taking down the existing tool, it will continue to work as it does currently. We're just acknowledging the fact that we have stopped maintaining it.

This one goes from `LibGit2Sharp.NativeBinaries-2.0.298` to `LibGit2Sharp.NativeBinaries-2.0.315-alpha.0.1` and that doesn't necessarily sound like a safe change. Though we've had "discussions" with the LibGit2Sharp team before about their versioning scheme...

I've generated some automated updates... and yes, the pipeline is failing. I'll see if I can work out why.

@arikalish this looks IMO like it was a test failure and was solved by #1113 - could you please update from main branch again?

I'd like to dig into this a bit more before going "OK". @msallin I'm not fond of "accidental features" like this - there's dedicated tools to trim the dependencies tree.

I use ReSharper for this, but seems that VS also has this built-in now https://stackoverflow.com/a/67715612/3205 . I've also used `dotnet-outdated` for this purpose before https://github.com/dotnet-outdated/dotnet-outdated#reporting-on-transitive-dependencies

@slang25 the catch with this approach - and the reason we avoided it before - is that it doesn't work with .NET Framework Classic. And at least when we looked...

@msallin I'm offline for the night, I'll have a look tomorrow, if that's ok. I have free time tomorrow.

I'm only concerned how this interacts with #311 and #466 . NuKeeper should currently skip unversioned packages (yes, I know those went away now, but the tag without a version...

Note: because of the hard dependency on `Newtonsoft.Json`, out of the box `JsonApiFramework` does not behave as expected on .NET Core 3.0/3.1 (the serialisation format doesn't match as `Newtonsoft.Json` attributes...