-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
deps(snyk): update snyk snapshot #5890
deps(snyk): update snyk snapshot #5890
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
|
I signed it! |
I believe it's based solely on the email address in every commit, did snyk-bot's email address for commits change? |
I don't see the snyk-bot's email address in the individual CLAs list, but #5774 did pass before and appears to have used that same email address, so something else changed, maybe? Did you all recently switch to a corporate CLA? I see "Snyk Ltd" in that list, so I believe the process in https://cla.developers.google.com/about#add-contributors should work to add snyk-bot (if it isn't added and something is just going wrong). |
@aviadatsnyk see "How do I add authorized contributors for my company?" on https://cla.developers.google.com/about#add-contributors I suspect that is the fix for this. If the bot account is already in the group I can email people here to debug further. thanks! |
@aviadatsnyk ping. did you get a change to look at the group membership? |
sorry for dropping the ball on this one - looking at it now. |
fixed on our end. #6074 |
thanks @aviadatsnyk! |
Why this PR?
a weekly update of the vulnerabilities snapshot for lighthouse