My JSON:API framework Felicity has a dependency on FSharp.SystemTextJson.
Currently I am pinning the exact version of FSharp.SystemTextJson, including the patch version. But if you know that during 0.x you will always bump the minor version (not just the patch version) on binary breaking changes, I can relax this constraint to support any patch version and just lock the minor version.
Of course, it has only rarely happened that FSharp.SystemTextJson has had multiple patch releases for a given minor release, so the issue may be a bit theoretical, but I'm asking anyway. :)
cmeeren
commented
1 year ago
My JSON:API framework Felicity has a dependency on FSharp.SystemTextJson.
Currently I am pinning the exact version of FSharp.SystemTextJson, including the patch version. But if you know that during 0.x you will always bump the minor version (not just the patch version) on binary breaking changes, I can relax this constraint to support any patch version and just lock the minor version.
Of course, it has only rarely happened that FSharp.SystemTextJson has had multiple patch releases for a given minor release, so the issue may be a bit theoretical, but I'm asking anyway. :)