I'm not sure I agree that the phrase "going stable" really applies to a semver project. The most stable release would just be the highest number in each segment. Version 1.0.1 is almost by definition going to be more stable than 1.0.0, since the changes are only backwards-compatible bug fixes. At least that's my understanding of semver.
> Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
(Yes, this means that you can use 0.x and declare yourself "semver compatible" and break on any patch release)
That being said it's possible to change a library's behaviour without touching the API. Consider the following diff:
-add a b = a + b
+add a b = a - b
Granted the example is simplistic. With the API versioning system in place the author should have renamed the method and would have gotten the right result. It's just to show that it wouldn't be a silver bullet.That said, it might be the case that removing the responsibility of versioning from experts would make them less concerned about the ramifications, and less likely to notice when they make a change like this one (well not this one exactly, but one similar but more reasonable).
You really do need tests in addition to static analysis to be sure of these things.
Plus, it gives a degree of reliability to those using the packages, which is something you can't necessarily count on in Haskell right now.
This is very interesting to me. It demands consideration: do we need a person to manually bump the version anymore at all? If you can statically verify that a change meets the criteria, couldn't the package publishing process autoincrement the appropriate version segment and be done with it?