Azuqua uses Semantic Versioning to version connectors. You have three numbers: a major version number, a minor version number, and a patch number. Each number is separated by decimals, and they provide information about the magnitude of the change made in each version.
For example, the first time you build a connector, you might submit version number 1.0.0. Then, you need to make a patch to fix a bug, so you submit version 1.0.1 and 1.0.2 as you debug your work. Later on, you decide to add a card. Since this is a bigger change but it’s still backward-compatible, you release version 1.1.0. Then in a few months, your application gets a new version of the connector and it needs a complete rebuild. This will be released as version 2.0.0 and so on.
How your team uses version numbers to track changes is up to you. Currently, the our platform’s engine does not pay any attention to version number, it only runs Flows on the most recently published version of the connector.
While you are working on a connector, the version you are changing is kept as ‘DRAFT’, and can be accessed from the bottom of the version tab by the connector name. Every time you save edits they over-write the most recent version and save to ‘DRAFT’. To capture a version of a connector, increment the version number and hit “Submit.” This will build the current draft of the connector and save it in a separate location, so it can’t be overwritten. It will now appear in the Control Panel so an administrator can deploy it to an environment.