Skip to content

Commit

Permalink
(build) Use rc prerelease label
Browse files Browse the repository at this point in the history
When there is no prerelease label, it means we are building on the
master branch, however, when we are not tagged, we still need this
label, otherwise, building the packages fails.  Let's use the rc
(Release Candidate) label.  i.e. building on develop gives us alpha
packages, building on hotfix/release branches gives us beta packages,
and building on master branch without a tag, gives us rc packages.
  • Loading branch information
gep13 committed Apr 27, 2022
1 parent fe89056 commit f98641b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions BuildScripts/default.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -69,8 +69,8 @@ task Run-GitVersion {
$script:packageVersion = $versionInfo.LegacySemVer
$script:informationalVersion = $versionInfo.InformationalVersion
} else {
$script:packageVersion = "$majorMinorPatch" + $(if ($prerelease) { "-$prerelease" }) + "-$buildDate" + $(if ($counter) { "-$counter" })
$script:informationalVersion = "$majorMinorPatch" + $(if ($prerelease) { "-$prerelease" }) + "-$buildDate-$sha"
$script:packageVersion = "$majorMinorPatch" + $(if ($prerelease) { "-$prerelease" } else { "-rc" }) + "-$buildDate" + $(if ($counter) { "-$counter" })
$script:informationalVersion = "$majorMinorPatch" + $(if ($prerelease) { "-$prerelease" } else { "-rc" }) + "-$buildDate-$sha"
}

Write-Host "Assembly Semantic Version: $version"
Expand Down

0 comments on commit f98641b

Please sign in to comment.