Verified75% confidenceFactExact time
In semantic versioning, a major version number of 0 (e.g., 0.1.7) conventionally indicates that the public API is not yet stable and may change in a non-backward-compatible manner at any time.
3
Sources
75%
Confidence
Long-term
Relevance
9/27/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedUnder the SemVer specification, when the major version number is 0, it means the project has not yet entered a stable public API phase and provides no backward compatibility guarantees70% similarUnverifiedPatch versions follow semantic versioning specifications, contain no breaking changes, and do not introduce new public APIs.69% similarUnverifiedIn the Semantic Versioning specification, incrementing the major version number (MAJOR) is specifically used to indicate incompatible changes to the existing public API.67% similarUnverifiedInternal REST interfaces carry no versioning guarantees and are not protected by service agreements; vendors can modify or shut them down at any time, making them less stable than officially public APIs.66% similarVerifiedIn the Semantic Versioning (SemVer) specification, the version format is MAJOR.MINOR.PATCH, and incrementing the major version number is used to indicate incompatible changes to the existing public API.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/954572API
curl https://kongchang.com/api/v1/knowledge/claims/954572MCP
get_claim(id=954572)