I am wondering if that fix (published in 2.16) should have been a major version change? My problem is that the first nuget is automatically upgrading to the later minor versions assuming them to be backwards compatible.
Probably too late to fix now. But I thought I would note that it is causing issues (at least for me).
The fix to issue https://github.com/kevin-montrose/Jil/issues/279 causes a conflict when an application uses 2 NuGets that use this library when:
Basically, the pre-change dependency is looking for a jil.core assembly and cannot find it in the newer version. (See this stack overflow question for details: https://stackoverflow.com/questions/60609571/nuget-package-is-looking-for-exact-version).
I am wondering if that fix (published in 2.16) should have been a major version change? My problem is that the first nuget is automatically upgrading to the later minor versions assuming them to be backwards compatible.
Probably too late to fix now. But I thought I would note that it is causing issues (at least for me).