The versioning scheme describes how we assign and increment version numbers. It clarifies the meaning of major, minor, and patch releases, how we handle breaking changes, and the role of pre-release tags. By following this structure, you can anticipate the impact of each update and plan migrations confidently.

​
Semantic versioning

We follow a modified semantic versioning scheme in the format X.Y.Z [-designation], where:
Version typeIncrement frequencyCharacteristicsExample
X (Major Version)Evaluated every two development cycles, but only released if there are significant changes.May introduce breaking changes.

Requires explicit upgrade steps.		1.0.0 → 2.0.0
Y (Minor Version)Every development cycleMaintains backward compatibility.

Introduces new features and functionality.		1.0.0 → 1.1.0
Z (Patch Version)As needed, outside the regular cycleFor hotfixes, security patches, and critical updates.

Maintains backward compatibility.		1.1.0 → 1.1.1