Use consistent semver for lazygit versioning

[leucos]

Is your feature request related to a problem? Please describe.

Current versioning uses only Major.Minor for first minor release; e.g. 'v0.32'.

However, the versioning scheme switches to Major.Minor.Patch afterwards (e.g. 'v0.32.1').

This makes it difficult to automate installations with tools that strictly enforce consistent versioning (e.g. binenv).

Describe the solution you'd like

It would be great to have all release containing Major.Minor.Patch (e.g. 'v0.32.0' instead of 'v0.32').

[jesseduffield]

I'm happy to do that from here on.

[jesseduffield]

Will close this issue after the next release

[leucos]

Thanks for the change @jesseduffield !
However I have another question regarding versioning.

The latest version is "v0.35" (e.g. "major.minor" scheme) while there was a v0.32.2 ("major.minor.patch" scheme) in January this year.

Do you plan to stick to "major.minor" scheme from now on ?

[ChrisMcD1]

/close

All current releases are released an v0.X.X (with v0.49.0 as a recent example)

For all future searchers of this issue, know that LazyGit doesn't actually follow SemVer at time of writing. We just cut and release a new build off a master if we find a bug in the last release, and tag that as a patch version, since it likely doesn't include new features. We aren't cherrypicking bugfixes back into an old branch, and we never release a v0.48.1 after we have released a v0.49.0.