When we developed the current archetype versioning rules, based on Semver, the rules around unpublished artefact version tracking in Semver was (and still remains) pretty loose.
We decided to live with that in the context of CKM as it uses MD5 hashing to ensure proper ‘hook-up’ of versions e.g archetypes in templates, and from the perspective of CKM editors/reviewers, strict version tracking is not that useful.
However, at application dev level, where we are often doing things pretty fast, it is becoming increasingly important to identify breaking changes , or potential breaking changes both to modellers and downstream artefacts.
We probably do not want to break the .v0 commitment - to make it very clear that this is a draft artefact but need to shoehorn the major.minor identifiers in there in a consistent way that can be applied cross-tooling.
One option is to shift-right the major.minor numbers
V0.major.minor.patch breaks semver rules but I could probably live without carrying patch (only really matters if translations are added).
when published we would always jump to V1.1.0, regardless of where we got to in the V0 cycle.
Fabio is busy implementing semver in Archetype Designer so early consideration would be helpful.