Template Lifecycle
Understanding template versions, updates, and deprecation
Template Lifecycle
Versioning
Templates use auto-incrementing integer versions (1, 2, 3, ...).
Each time you publish a template with cyanprint push, a new version is automatically created with the next integer. Version numbers have no semantic meaning - they simply track the order of publication.
Updates
When a template is updated, you can use the cyanprint update command to bring your project up to date while preserving your customizations.
The "latest" version refers to the highest integer version number available in the registry, not semantic versioning.
See Update a Project for the how-to guide.
Deprecation
Workaround for Deprecation
Template deprecation is not currently supported. To indicate a template is no longer maintained, update the template description or readme to note this.