-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Address security advisories #3280
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
I have read the CLA Document and I hereby sign the CLA |
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.
LGTM. But does this need some kind of regression since some library versions a resolved to a specific version?
I think that makes sense. @cortisiko & @ibrahimtaveras00 Do you think we can cover this in the next release regression? |
ddb2af1
to
6f9dca2
Compare
Description
A whole slew of advisories came in recently. this PR addresses those. the ones that could be upgraded have been and the ones that could be addressed via resolutions also have been. there are a couple cases where there have yet to be any resolutions and so those have been ignored until we can come up with a better solution.