Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NET-8174] security: add triage alias for GO-2024-2554 (1.4.0) #3704

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

zalimeni
Copy link
Member

@zalimeni zalimeni commented Feb 29, 2024

This vulnerability was already triaged via its GHSA alias, but the scanner is flagging it under this name, so adding an explicit entry.

PR for main and release branches: #3705

How I've tested this PR

Scanner now passes locally.

How I expect reviewers to test this PR

👀

This vulnerability was already triaged via its GHSA alias, but the
scanner is flagging it under this name, so adding an explicit entry.
@zalimeni zalimeni force-pushed the zalimeni/triage-helm-GO-2024-2554-1.4.0 branch from a9af8de to b52dd36 Compare February 29, 2024 19:59
Copy link
Contributor

@DanStough DanStough left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@zalimeni zalimeni added pr/no-changelog PR does not need a corresponding .changelog entry pr/no-backport signals that a PR will not contain a backport label labels Feb 29, 2024
@zalimeni zalimeni enabled auto-merge (squash) February 29, 2024 20:01
@zalimeni zalimeni merged commit caee250 into release/1.4.0 Feb 29, 2024
30 of 56 checks passed
@zalimeni zalimeni deleted the zalimeni/triage-helm-GO-2024-2554-1.4.0 branch February 29, 2024 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-backport signals that a PR will not contain a backport label pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants