Applying the 'printSemVersion' task during release.

[Eteryz]

Hi

If you apply the 'releaseVersion' task and, for example, put tag 0.1.0, then the 'printInfoVersion' and 'printVersion' tasks output 0.1.0, but the 'printSemVersion' task outputs '0.1.0-sha.22f24d'.

There is such a situation:
For dev development we want to use versions '0.1.0-sha.22f24d'.
But when the release comes, we would like to drop the 'sha' part and get the answer '0.1.0'.

Can we add the 'enableShaRelease' flag, which will be 'true' by default? (Can be called differently: includeShaInRelease, includeCommitHashInRelease)
If 'enableShaRelease'= true and we have a release, then the 'printSemVersion' task will produce the result as before '0.1.0-sha.22f24d1'.
If 'enableShaRelease'= false and we have a release, then the 'printSemVersion' task will produce the following result:
'0.1.0'.

[jmongard]

Hi,

I'm not sure exactly what is missing in the existing print tasks.
If you don't want the sha part just use printVersion?

If you want to print the version with sha but without the commit count you can define your own print task e.g:

tasks.register("printVersionSha") {
     println(semver.semVersion.toInfoVersionString(
             commitCountStringFormat = "", shaLength = 7, metaSeparator = '-'))
}

Or is there some other problem you need help with?

[Eteryz]

Hi.
I just would like that during the release (git commit --allow-empty -m "release: v0.1.2") when I use the command "gradle printSemVersion -q> version.txt " in Gitlab CI
I had 0.1.2 there, and when there is no release, and just test builds, 0.1.2 would fit there-sha.22f24d