.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 <[email protected]>
cilium · Jun 26, 2023 · a74d624 · a74d624
1 parent b95423a
commit a74d624
Showing 1 changed file with 3 additions and 1 deletion.
diff --git 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