From a74d6246317b6aef0d7e72bf74ba6a08f713a580 Mon Sep 17 00:00:00 2001 From: Quentin Monnet Date: Mon, 26 Jun 2023 11:04:04 +0100 Subject: [PATCH] .github/release_patch: Reach out to @cilium/security for advisories It's not clear where to get the list of advisories from, when we need to mention them in the release notes. Tell users they should check with @cilium/security. We still miss a hint on how to reach out to this team, though. Signed-off-by: Quentin Monnet --- .github/ISSUE_TEMPLATE/release_template_patch.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/release_template_patch.md b/.github/ISSUE_TEMPLATE/release_template_patch.md index c01204a..9098649 100644 --- a/.github/ISSUE_TEMPLATE/release_template_patch.md +++ b/.github/ISSUE_TEMPLATE/release_template_patch.md @@ -89,7 +89,9 @@ assignees: '' successful. - [ ] Check draft release from [releases] page - [ ] Update the text at the top with 2-3 highlights of the release - - [ ] Include the list of security advisories at the top. + - [ ] Check with @cilium/security if the release addresses any open security + advisory. If it does, include the list of security advisories at the + top of the release notes. - [ ] Copy the text from `digest-vX.Y.Z.txt` to the end of the release text. This text was previously generated with `contrib/release/post-release.sh`, or is otherwise available in the