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
[bp/1.25] Backport stack #28441
[bp/1.25] Backport stack #28441
Conversation
Fix envoyproxy#28261 Signed-off-by: Ryan Northey <ryan@synca.io>
CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to |
Signed-off-by: Ryan Northey <ryan@synca.io>
@phlax how come we are backporting non-critical dependency changes? |
there are a few deps that are in the intersection of a) deps that issue CVEs, and b) deps that we have correctly configured to track - wasm/rust/kafka in particular historically we have had to update/backport these deps in response to the CVEs, so now i just always backport them |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack, thanks.
Signed-off-by: wbpcode <wangbaiping@corp.netease.com> Signed-off-by: Ryan Northey <ryan@synca.io>
landing to fix branch |
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]