IMPORTANT: This documentation has been discontinued. Read the updated Capsules - FAQ documentation on our new documentation portal.
To ensure reliability in the Capsules updates, Digibee has adopted a versioning control composed of 3 levels. When the versions need to be updated, the Digibee HIP Platform analyzes a Capsule automatically and determines which will be the values of the levels.
These are the 3 versioning levels:
Major: Capsule version when a configuration item (input or output) is removed or becomes mandatory. This version is also applicable when the Capsule contract is totally modified. The direction for this version is made automatically by the Platform itself.
Minor: Capsule version when a configuration item (input or output) is added or becomes optional. This change isn’t considered "Major" yet.
Fix: version of the Capsule when minor changes are made in the pipelines that use it. This change isn’t considered "Major" or "Minor".
It’s important to know that these changes will only be made if the version going through the change has already been published. For example, if you create a Capsule, it will initially receive the version "1.0.0". As long as it’s not published, this version will never be modified when updates are made to it.
After the publication of the Capsule, the version "1.0.0" will be defined as not editable. Then, when a new update is made in the same Capsule, the Platform will analyze what has been changed to determine if the version number will be added in the Major, Minor or Fix version.
Click here to see more questions about Capsules.