diff --git a/RELEASE.md b/RELEASE.md
index 36c6fbc5f..6bb8eb3b3 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -7,6 +7,7 @@ The Kubespray Project is released on an as-needed basis. The process is as follo
 1. (Only for major releases) Keep Kubernetes binary checksums and per-minor component mappings for the default Kubernetes minor and the two previous minors (a support floor of `n-2`). The oldest `kubelet_checksums` entry determines `kube_version_min_required`.
 1. (Only for major releases) Remove hashes for [EOL versions](https://github.com/kubernetes/website/blob/main/content/en/releases/patch-releases.md) of kubernetes from `*_checksums` variables.
 1. Create the release note with [Kubernetes Release Notes Generator](https://github.com/kubernetes/release/blob/master/cmd/release-notes/README.md). See the following `Release note creation` section for the details.
+1. Before tagging `vX.Y.Z`, run GitLab `daily-ci` for the release commit and verify the pipeline's commit SHA matches. Link the pipeline in the release issue and review any jobs marked `allow_failure`.
 1. An approver creates [new release in GitHub](https://github.com/kubernetes-sigs/kubespray/releases/new) using a version and tag name like `vX.Y.Z` and attaching the release notes
 1. (Only for major releases) An approver creates a release branch in the form `release-X.Y`
 1. (For major releases) On the `master` branch: bump the version in `galaxy.yml` to the next expected major release (X.y.0 with y = Y + 1), make a Pull Request.