From ca5d867d72d4387e24828f3b5c81c352c6c4bcf2 Mon Sep 17 00:00:00 2001
From: VoigtS <s.voigt@sap.com>
Date: Fri, 6 Oct 2023 17:53:13 +0200
Subject: [PATCH 1/2] v0.9.5


From 06360337441a0c2e61cb078851cd59e9a7972a96 Mon Sep 17 00:00:00 2001
From: VoigtS <s.voigt@sap.com>
Date: Mon, 9 Oct 2023 10:24:35 +0200
Subject: [PATCH 2/2] RELEASE.md: Add envtest binary info to create new release

---
 RELEASE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RELEASE.md b/RELEASE.md
index 59f34960..6b61791d 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -1,7 +1,7 @@
 # Release Guide
 
 1. Ensure local `master` branch is up to date with `origin/master`.
-2. Ensure all checks are passing: `make check`.
+2. Create the Evntest environment with `make prepare-envtest-binaries`. Ensure all checks are passing: `make check`.
 3. Update the [`changelog`](./CHANGELOG.md). Make sure that the format is consistent
    especially the version heading. We follow [semantic versioning][semver] for our
    releases.