The binaries built by the release action include the commit hash in their version

[ejpcmac]

Problem description

If I run a binary downloaded from the release page and print its short version, I get the following:

$ ./git-z-0.2.1-x86_64-unknown-linux-musl -V
git-z 0.2.1+e0e62f1

Expected behaviour

In releases, the short version should not contain the Git revision.

Analysis

In the different build jobs of the release action, the Git repository is cloned using actions/checkout@v4 without any parameter. By default, this only does a shallow clone, which does not include tags. Hence, the build.rs is not able to check whether the build is made from a tag matching the version, and the revision is then included.

Solution

Set fetch-tags: true in the parameters for actions/checkout@v4 for the build-bin, build-deb and build-msi jobs.

^ This solution makes the fetch fail. Replacing it with fetch-depth: 0 makes the build work again, but… does still include the hash.

[ejpcmac]

Actually this is not solved 😭

$ ./git-z-0.2.2-x86_64-unknown-linux-musl -V
git-z 0.2.2+45b8aee