Verified85% confidenceFactExact time
In 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.
5
Sources
85%
Confidence
Long-term
Relevance
7/6/2026
First Seen
Sources
Claude Leads sqlite-utils 4.0 Development for $149: A Real-World Look at AI Programming
hackernewshackernews7/5/2026
Related Claims
UnverifiedThe version number format of the Semantic Versioning specification (SemVer) is MAJOR.MINOR.PATCH, where the PATCH version is specifically used for backward-compatible bug fixes.78% similarUnverifiedIn the Semantic Versioning specification, incrementing the major version number (MAJOR) is specifically used to indicate incompatible changes to the existing public API.76% similarVerifiedThe Semantic Versioning format is MAJOR.MINOR.PATCH: MAJOR is incremented for incompatible API changes, MINOR is incremented when backward-compatible new features are added, and PATCH is incremented for backward-compatible bug fixes.73% similarVerifiedThe Semantic Versioning (SemVer) format is MAJOR.MINOR.PATCH: a change in the major version number indicates backward-incompatible API changes, a change in the minor version number indicates new features that maintain backward compatibility, and a change in the patch number includes only bug fixes.69% similarUnverifiedIn semantic versioning, incrementing the MAJOR version (e.g., 3.x→4.0) indicates the inclusion of breaking changes, such as deleting or renaming public APIs or modifying function signatures.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/114227API
curl https://kongchang.com/api/v1/knowledge/claims/114227MCP
get_claim(id=114227)