fix: Remove multiple SemVer incompatibilities in tagFormat #3309
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current implementation is non SemVer compliant in many cases. For example:
v${version}a
to a valid tag even though it is NOT a valid SemVer tagThis PR addresses this issue by making sure that when analysing tags, and when publishing them, SemVer compliance is mostly followed.
Mostly because there is 1 notable exception – any prefix is allowed preceding the
${version}
. So, even thoughpre-1.1.1
is not strictly SemVer compliant – it is allowed.I would summarise this PR with the following table:
@travi please have a look. Apart from containing build meta – this PR does improve tag processing in various other ways making it more compatible with SemVer