![]() ![]() Somebody's always going to come along and want to add yet another. What you're trying to do is post release versioning, and that won't work. ![]() I have the impression that SemVer is generally unable or unsuitable to handle automatically generated version numbers, but what do you think of this idea of the fourth number anyway? At least Windows/.NET versions support this. Now while the spec says that four numbers are invalid, it could easily be interpreted in a way that leads to a correct sort order with four numbers. (You never know when after the tag "v1.0" a tag "v1.0.1" will appear, so the third number should not be used for this.) But that could easily (and probably even should always) lead to a fourth number. Maybe with a "-something" to declare it as pre-release. The cleanest solution would be to append the number of commits after the mentioned tag after another dot. In-order, but all on the wrong side of the tagged version. This obviously completely goes against SemVer because my newer commits will then be considered older. If the current commit is after a version tag, then the version will be the tag name, appended with "-" and the number of commits after the tagged commit, like "v1.1-5" for 5 commits after v1.1.If the current commit has a version tag, then this will be the version.I've previously implemented that like following: I'm looking for a solution to automatically label commits that are after a version tag of the kind "v1.1" or "v2.4.3". I see that the spec is pretty clear about only allowing exactly three numbers, separated by a dot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |