Versions
The version for mu follows Semantic Versioning. In summary:
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
- Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
Anytime mu attempts to update a stack, it first checks what version of mu was used to create the stack. If the MAJOR number does not match that of the current version of mu that is running, then an error will be reported. This is due to the fact that there may be issues with updating your existing stack with the latest CloudFormation templates from mu. If you wish to proceed and force the update, you can pass in a -F to your mu command to skip version number checking. CAUTION: do this at your own risk!