From 369f733a36ee291a2a339d2605741ab8b142de92 Mon Sep 17 00:00:00 2001 From: Luca Guerra Date: Tue, 9 May 2023 12:57:55 +0000 Subject: [PATCH] update(docs): clarify release checking in the readme Signed-off-by: Luca Guerra --- RELEASE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/RELEASE.md b/RELEASE.md index 0a205ccd..76857db2 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -129,6 +129,8 @@ To do so: - Publish the prerelease! - The release pipeline will start automatically. Packages will be uploaded to the `-dev` bucket and container images will be tagged with the specified tag. +In order to check the status of the release pipeline click on the [GitHub Actions tab](https://github.com/falcosecurity/falco/actions?query=event%3Arelease) in the Falco repository and filter by release. + ## Release Assume `M.m.p` is the new version. @@ -179,6 +181,8 @@ Assume `M.m.p` is the new version. - Finally, publish the release! - The release pipeline will start automatically upon publication and all packages and container images will be uploaded to the stable repositories. +In order to check the status of the release pipeline click on the [GitHub Actions tab](https://github.com/falcosecurity/falco/actions?query=event%3Arelease) in the Falco repository and filter by release. + ### 2. Update the meeting notes For each release we archive the meeting notes in git for historical purposes.