Open ErinvanderVeen opened 11 months ago
Thankfully this doesn't impose any significant change on our versions:
Other changes. Otherwise, e.g. if change consist only of corrected documentation, non-visible change to allow different dependency range etc. A.B.C MAY remain the same (other version components may change).
As always, I recommend against upper bounds altogether (unless an actual incompatibility is known). They create a non-trivial amount of gratuitous work, and rarely actually help. But I won't fight for it.
I'd say let's just leave this issue open for now and not spend any effort on this until we run into actual problems (e.g. when we have users complain that the bounds are too strict)
When publishing, Hackage warned about the following, this should be resolved for a next release.