From e2669d4acce75791aa5b5ce912cb1a36377993f0 Mon Sep 17 00:00:00 2001
From: stevenhorsman <steven@uk.ibm.com>
Date: Wed, 18 Dec 2024 11:03:46 +0000
Subject: [PATCH] release: Abort if release version exists

In order to check that we don't accidentally overwrite
release artifacts, we should add a check if the release
name already exists and bail if it does.

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
---
 tools/packaging/release/release.sh | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/tools/packaging/release/release.sh b/tools/packaging/release/release.sh
index 9dcf570718..00ec2b76a6 100755
--- a/tools/packaging/release/release.sh
+++ b/tools/packaging/release/release.sh
@@ -63,7 +63,7 @@ function _create_our_own_notes()
 	libseccomp_version=$(get_from_kata_deps ".externals.libseccomp.version")
 	libseccomp_url=$(get_from_kata_deps ".externals.libseccomp.url")
 
-	cat >> /tmp/our_notes_${RELEASE_VERSION} <<EOF 
+	cat >> /tmp/our_notes_${RELEASE_VERSION} <<EOF
 ## Survey
 
 Please take the Kata Containers survey:
@@ -112,6 +112,11 @@ function _create_new_release()
 
 	RELEASE_VERSION="$(_release_version)"
 
+	if gh release view ${RELEASE_VERSION}; then
+		echo "Release already exists, aborting"
+		exit 1
+	fi
+
 	_create_our_own_notes
 
 	# This automatically creates the ${RELEASE_VERSION} tag in the repo