3 ms·
Interestingly, being `0.y.z` as a major released version (e.g. not in development or a release candidate) does seem to break semver[1], but I do realize it's mo
by dvt 4y ago
Interestingly, being `0.y.z` as a major released version (e.g. not in development or a release candidate) does seem to break semver[1], but I do realize it's more of a guideline and no one really cares:
> Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. It MAY also include minor and patch level changes. Patch and minor versions MUST be reset to 0 when major version is incremented.
[1] https://semver.org/ https://semver.org/
- bitdivision 4y agoFor versions < 1.0.0 this does not apply: > Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.