grpc update

[ghost]

Fixes #1753

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. 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, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[stephenplusplus]

Thank you! We don't require specifying this, however. If you un- and re-install google-cloud (or one of the sub-modules, i.e. @google-cloud/bigtable), it will pick up the latest 1.0.1. Can you try this and confirm?

[ghost]

Try to uninstall and reinstall google-cloud. grpc still on 1.0.0

[googlebot]

CLAs look good, thanks!

[stephenplusplus]

Yep, that is weird. Installing @google-cloud/bigtable pulls down the latest. It's acting as if we have a hard dependency on grpc@1.0.0 somewhere, but I don't know where. @callmehiphop any ideas?

[coveralls]

Coverage remained the same at 100.0% when pulling d044f2d on Turismatic:grpc-update into 56c745b on GoogleCloudPlatform:master.

[stephenplusplus]

Mystery solved. We shrinkwrap our google-cloud release, so 1.0.0 is hardcoded as the dependency to install. All of our dependencies, including grpc, will be updated before we shrinkwrap for our next release, so this change isn't necessary. Thanks for calling this out, we hope to have a release out after some more PRs merge.