doom-neovim/doom-nvim

[BUG] git tag version sort shows v4.0.0-alpha6 as latest

edwintorok opened this issue · 1 comments

edwintorok commented

Please create a v4.0.1 or v4.0.2 tag, currently if I'd follow the README to create a my-config tag I'd end up branching off from v4.0.0-alpha6.
See below for details

Current Behavior:

git tag -l --sort -version:refname | head -n 1
v4.0.0-alpha6

Expected Behavior:

v4.0.1

Steps To Reproduce:

git tag -l --sort -version:refname | grep 4.0
v4.0.0-alpha6
v4.0.0-alpha5
v4.0.0-alpha4
v4.0.0-alpha3
v4.0.0-alpha2
v4.0.0-alpha1
v4.0.0
v.4.0.1

And v.4.0.1 looks like a typo, did you mean v4.0.1?

Logs

Anything else:

The alpha suffix doesn't have the desired effect, this is explained in the manual:
https://git-scm.com/docs/git-config/2.19.2#Documentation/git-config.txt-versionsortsuffix

However by creating a v4.0.1 or v4.0.2 tag that shouldn't be an issue anymore: they'll be the latest and not the alpha tags.

connorgmeehan commented

Hey thanks for posting this, I didn't see this issue but I have addressed this earlier and double checked that the auto-updater works with the v4.0.1 tag. :)