Everytime an automation is pushed from the CLI, a new version (revision) is created. The first time an automation is registered through the CLI, it will be assigned a semver version of 0.0.1. Any subsequent pushes must be manually assigned a successive version, of which you can choose major, minor, or patch. Automation owners will always use the latest version of an automation regardless of if the latest revision is assigned a semver version. However, for publicly shared automations on the Hub, installers will only be able to install the latest version which is assigned a semver version. Upon creating a new semver version, public installers will not install it automatically and must opt-in to the new version.