2 ms·
there are probably cases in which you want to change the version independently of API changes, i.e. "going stable" (0.x to 1.0), major internal changes, new int
by riffraff 12y ago
there are probably cases in which you want to change the version independently of API changes, i.e. "going stable" (0.x to 1.0), major internal changes, new interfaces with deprecations of the old ones etc.
- couchand 12y agoGood point, you still need an escape hatch to bump a version segment higher than the minimum necessary one, for many reasons. 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.
- riffraff 12y agosemver has a special case for 0.x, which is basically "before 1.0 there are no guarantees". In their words: > 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)