.github/templates: point security pre-check at cilium/security blockers - #429
Merged
Conversation
The pre-check item asked the release manager to check with the @cilium/security team whether there are any security fixes to include in the release, which requires an out-of-band conversation and gives no way to tell when the check is actually done. Security fixes that must land before a release are already tracked as issues labeled release-blocker/X.Y in cilium/security, so point the item directly at that query instead. Add a [cilium/security] link reference next to the existing [release blockers] one so the X.Y placeholder gets substituted with the target version, and regenerate the goldens. The CVE-in-the-image item above it still requires talking to the security team, as those findings are not tracked as issues. Signed-off-by: André Martins <andre@cilium.io>
joestringer
approved these changes
Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pre-check item asked the release manager to check with the @cilium/security team whether there are any security fixes to include in the release, which requires an out-of-band conversation and gives no way to tell when the check is actually done.
Security fixes that must land before a release are already tracked as issues labeled release-blocker/X.Y in cilium/security, so point the item directly at that query instead. Add a [cilium/security] link reference next to the existing [release blockers] one so the X.Y placeholder gets substituted with the target version, and regenerate the goldens.
The CVE-in-the-image item above it still requires talking to the security team, as those findings are not tracked as issues.