How broad or narrow should the usage dependency version constraints be?
2 answers
There is a package version policy of the Haskell package that gives clear guidelines.
But I must add that they are not universally accepted and generate a regular heated debate, especially the top version related to dependencies.
+1
source to share
It really depends on your dependencies. If you're lucky, they enforce semver conventions correctly , in which case you should install your dependency with the earliest minor version your projects are running and anything after, but before the next major version.
+1
source to share