-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
node 12 -> node 16, grpc -> grpc-js #630
Conversation
🚲 PR staged at http://34.73.14.146 |
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.
Thank you for the change. Left a comment!
🚲 PR staged at http://34.73.14.146 |
I have updated the PR with some minor improvements. The diff between the last commit from the author and all my commits can be viewed at this link: |
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.
I have tried skaffold dev
and did a quick manual test of my deployment (on my GKE cluster).
The changes also look good, and yes, Node.js 16 is the way to go today.
Approved!
Thanks, @Shabirmean, for taking over this pull-request and tidying it up. 🙏
This reverts commit 3f437db. linked to issue 647
This reverts commit 3f437db. linked to issue 647
I came across these upgrades while trying to fix #538 - our Node and grpc JS versions were out of date and/or deprecated. This turned out to not be the cause of the memory leak but we should probably still upgrade.
changelog
grpc
togrpc-js
.grpc
is deprecated. See Migrating to grpc-js for thebind-async
change you see in this PR.