Capsules versioning
Learn more about how Capsules are versioned in the Digibee Integration Platform.
Capsules have a version control consisting of 3 levels represented by: 1.0.0. The first number is called “Major”, the second number is called “Minor”, and the third number is called “Fix”.
When versions need to be updated, the Digibee Integration Platform automatically analyzes the Capsule after each change to determine versioning level values.
See how the levels are determined:
Fix: version of the Capsule when no impactful changes are made in the pipelines that use it. It increments Fix by 1 (0.0.1).
Minor: version of the Capsule when a configuration item (input or output) is added or becomes optional. Increases Minor by 1 (0.1.0).
Major: version of the Capsule when a configuration item (input or output) is deleted or becomes mandatory. This version is also applicable when the Capsule contract is completely changed. It increases Major by 1 (1.0.0).
These changes are only made if the changed version has already been published. For example, if you create a Capsule, it will initially be given the version "1.0.0". If you don’t publish it, this version will never change, regardless of whether you make updates to the Capsule or not.
After you publish the Capsule, the version “1.0.0” is defined as not editable. When a new update is made in the same Capsule, the Platform checks what has been changed to determine if the version number should be added to Major, Minor or Fix.
The version number is displayed next to the Capsule name.
![Capsule environment, with the version of the Capsule appearing next to the name of the Capsule.](https://docs.digibee.com/~gitbook/image?url=https%3A%2F%2F2041393763-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F4523BaA7JfghHEYBbLWY%252Fuploads%252FHOhNy8hhsFnvTafMDOCD%252Fcapsules-versioning-2.png%3Falt%3Dmedia%26token%3Dd4964c1e-d520-4bec-b7f5-3011521ae6d5&width=768&dpr=4&quality=100&sign=9954b233&sv=1)
Last updated