On Sun, 04 Mar 2018 19:39:29 GMT, ParticlePeter wrote:
On Sun, 4 Mar 2018 13:35:26 +0100, Sönke Ludwig wrote:
AFAIK, this is the best thing that can be done within SemVer. The
suffix is specified to have no semantic meaning in terms of version
precedence (using "SHOULD" notation, though). But regardless, the
regular version must indeed always be incremented to make upgrading work
Does this mean that the parsing of SemVer is not customize-able on your side?
So how about e.g. and optional secondary SemVer in the file format. It would not be possible to consider this secondary to trigger the update mechanics?