Current state
Currently the artifact 🧿 version string contains the --long output of git describe as retrieved in
|
$CommitName = & git describe --tags --long --match "v[0-9]*.[0-9]*.[0-9]*" |
and written into "$($SolutionDir)\Resources\BuildCommit.txt" at
|
$CommitName | Out-File -Force $BCommit -ErrorAction Ignore |
for any build, including tagged 🏷️ versions.
Reasoning
☝🏼 While this makes sense for preview builds (e.g. manually created locally or triggered through the "Run Workflow" button, cf. #5) it clutters up the name of a tagged release a bit without adding much value.
🤔 We could consider dropping those extra parts of the version string parts when building on a 🏷️ tag directly, but ONLY FOR THE ARTIFACT (meaning they should still be kept in the build metadata generated by Write-BuildDetails).
Goal
🏁 As a result, any tagged release would have artifacts like AutoTx-v3.1.1.zip instead of AutoTx-v3.1.1-0-g5aafd62.zip.
Current state
Currently the artifact 🧿 version string contains the
--longoutput ofgit describeas retrieved inauto-tx/Scripts/Prepare-Build.ps1
Line 106 in 6bb0e73
and written into
"$($SolutionDir)\Resources\BuildCommit.txt"atauto-tx/Scripts/Prepare-Build.ps1
Line 141 in 6bb0e73
for any build, including tagged 🏷️ versions.
Reasoning
☝🏼 While this makes sense for preview builds (e.g. manually created locally or triggered through the "Run Workflow" button, cf. #5) it clutters up the name of a tagged release a bit without adding much value.
🤔 We could consider dropping those extra parts of the version string parts when building on a 🏷️ tag directly, but ONLY FOR THE ARTIFACT (meaning they should still be kept in the build metadata generated by
Write-BuildDetails).Goal
🏁 As a result, any tagged release would have artifacts like
AutoTx-v3.1.1.zipinstead ofAutoTx-v3.1.1-0-g5aafd62.zip.