From c3f13265e4ed9cff3a53a2a00cea3c9057c5bd34 Mon Sep 17 00:00:00 2001
From: stevenhorsman <steven@uk.ibm.com>
Date: Tue, 17 Dec 2024 16:09:10 +0000
Subject: [PATCH] doc: Update the release process

Add a step to wait for the payload publish to complete
before running the release action.

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
---
 docs/Release-Process.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/Release-Process.md b/docs/Release-Process.md
index 354c948313..4eb15e3f5a 100644
--- a/docs/Release-Process.md
+++ b/docs/Release-Process.md
@@ -45,6 +45,14 @@ branch to read only whilst the release action runs.
 > [!NOTE]
 > Admin permission is needed to complete this task.
 
+### Wait for the `VERSION` bump PR payload publish to complete
+
+To reduce the chance of need to re-run the release workflow, check the
+[CI | Publish Kata Containers payload](https://github.com/kata-containers/kata-containers/actions/workflows/payload-after-push.yaml)
+once the `VERSION` PR bump has merged to check that the assets build correctly
+and are cached, so that the release process can just download these artifacts
+rather than needing to build them all, which takes time and can reveal errors in infra.
+
 ### Check GitHub Actions
 
 We make use of [GitHub actions](https://github.com/features/actions) in the