Proper release and strict version ranges for System.Text.Json and Microsoft.Extensions.Logging

[laped]

It's a problem with these strict version ranges for these packages, because if you have lots of other packages installed in a project that uses ZoomNet and are completely up-to-date and on .net 9 for example, some of those other packages will have something like Microsoft.Extensions.Logging >= 9.0.2 - which makes it impossible to upgrade this library to the latest version 0.87.0.

So my suggestion would be to bump those dependencies and then bump the major version of this library and do that each time there's a major version of the other dependencies - otherwise this library will quickly lose it's adoption among projects, if they cannot upgrade packages and are forced to downgrade instead.

I would also recommend to setting up dependabot to keep up with the dependency updates, that way it would automatically create a PR for those.

Let me know if you need any help.

References:

• Reference a range of versions for System.Text.Json and Microsoft.Extensions.Logging #387
• System and Microsoft dependencies versions for different TFM #386

[Jericho]

This issue is already documented in #391 and set to be fixed in version 0.88.0 which, coincidently, I am working on at this very moment.

[Jericho]

To be clear: setting the upper limit on the range to 9] was a mistake on my part. I intended to allow 9.*.* but I ended up allowing ONLY 9.0.0 which is way way way too restrictive. Clearly not what I intended. The fix included in 0.88.0 is to change the upper limit to 10) which allows any version in the 9 range.

I intend to test and verify whenever a new major version of the JSON library is released, make adjustments to resolve any breaking changes introduced in the new version and release a new version of ZoomNet with upgraded upper limit.

[Jericho]

Speaking of 0.88.0: it's currently being built in the CI environment and should be on NuGet within the hour (assuming everything goes according to plan).