summaryrefslogtreecommitdiff
path: root/hack/release.sh
diff options
context:
space:
mode:
authorW. Trevor King <wking@tremily.us>2018-06-01 13:53:41 -0700
committerAtomic Bot <atomic-devel@projectatomic.io>2018-06-01 21:39:45 +0000
commit96dc5fd0d5abb9a6edbc66a03c34b72958c14bb1 (patch)
treeca0a325137e9855e466b4c2819bb6372776ecf99 /hack/release.sh
parent500b94968b4e36a80540efa55f4c6be231464cce (diff)
downloadpodman-96dc5fd0d5abb9a6edbc66a03c34b72958c14bb1.tar.gz
podman-96dc5fd0d5abb9a6edbc66a03c34b72958c14bb1.tar.bz2
podman-96dc5fd0d5abb9a6edbc66a03c34b72958c14bb1.zip
hack/release.sh: Bump spec in dev_version_commit
Bump it to the next version (without a -dev suffix), based on the precedent set by 70672652 (Bump to v0.6.1-dev, 2018-05-25, #834). Previously I had VERSION there, which was a copy/paste error. I've also added an explicit write_spec_version to release_commit. That *should* be a no-op, with the spec version having already been set by the previous release's dev_version_commit. But better to be safe than to cut a release with the wrong version number in the spec file (e.g. maybe we guessed NEXT_VERSION wrong during the last release). Signed-off-by: W. Trevor King <wking@tremily.us> Closes: #879 Approved by: mheon
Diffstat (limited to 'hack/release.sh')
-rwxr-xr-xhack/release.sh3
1 files changed, 2 insertions, 1 deletions
diff --git a/hack/release.sh b/hack/release.sh
index 986e2b58b..6a91c098c 100755
--- a/hack/release.sh
+++ b/hack/release.sh
@@ -45,6 +45,7 @@ write_changelog()
release_commit()
{
write_go_version "${VERSION}" &&
+ write_spec_version "${VERSION}" &&
write_changelog &&
git commit -asm "Bump to v${VERSION}"
}
@@ -52,7 +53,7 @@ release_commit()
dev_version_commit()
{
write_go_version "${NEXT_VERSION}-dev" &&
- write_spec_version "${VERSION}" &&
+ write_spec_version "${NEXT_VERSION}" &&
git commit -asm "Bump to v${NEXT_VERSION}-dev"
}