Closed Johann-S closed 5 years ago
Maybe something you updated drops node 4 support?
Also, I'm not sure they want package-lock.json here since they seem to be using yarn.
You're right about package-lock.json đ But it's more related to Travis because I merged a PR this afternoon and same error
I sent a PR to drop node 4, then you can retry.
I'll update our packages again before merging this PR
So there's good news and bad news.
:thumbsup: The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.
:confused: The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.
Note to project maintainer: This is a terminal state, meaning the cla/google
commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla
label to yes
(if enabled on your project), and then merge this pull request when appropriate.
âšī¸ Googlers: Go here for more info.
All right, tests pass. We only need to solve the CLA thing @johnjbarton, then merge this, bump the minor version and release it.
Does anybody know how we can proceed with the CLA?
:frowning_face: Sorry, but only Googlers may change the label cla: yes
.
I guess we are stuck then. We could drop this PR and I can make one PR with only my patch which should pass.
Seems good to me đ
Update dependencies