Fix release script, it would create rc1 instead of rc.1 (#2383) (#2384)

* Dont put dot(.) between rc and number

* Revert "Dont put dot(.) between rc and number"

This reverts commit d9a8837bd0dc18a529d216f76b4f24fe588b63f7.

* Fix missed rc1 in release script

(cherry picked from commit 71f53a477a)

Co-authored-by: Tasos Boulis <tboulis@hotmail.com>
This commit is contained in:
Mattermost Build 2022-11-15 13:46:03 +02:00 committed by GitHub
parent fe50d79ad9
commit 1e38a538c3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -124,7 +124,7 @@ case "${1}" in
;;
"patch")
if [[ "${branch_name}" =~ "release-" ]]; then
new_pkg_version="${major}.${minor}.$(( micro + 1 ))-rc1"
new_pkg_version="${major}.${minor}.$(( micro + 1 ))-rc.1"
print_info "Releasing v${new_pkg_version}"
write_package_version "${new_pkg_version}"
tag "${new_pkg_version}" "Released on $(date -u)"
@ -147,7 +147,7 @@ case "${1}" in
exit 3
fi
new_pkg_version="${new_branch_version}.0-rc1"
new_pkg_version="${new_branch_version}.0-rc.1"
git checkout -b "${new_branch_name}"
write_package_version "${new_pkg_version}"
tag "${new_pkg_version}" "Quality branch"
@ -164,7 +164,7 @@ case "${1}" in
fi
new_branch_version="${major}.${minor}"
new_branch_name="release-${new_branch_version}"
new_pkg_version="${new_branch_version}.0-rc1"
new_pkg_version="${new_branch_version}.0-rc.1"
master_pkg_version="${major}.$(( minor + 1 )).0-develop"
print_info "Creating a new features branch: ${new_branch_name}"