Update google-proto-files to the latest version 🚀

[greenkeeper]

Version 0.16.0 of google-proto-files was just published.

Dependency	google-proto-files
Current Version	0.15.1
Type	dependency

The version 0.16.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of google-proto-files.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

v0.16.0

Features

• (#35): Allow passing load() options to protobuf.js. (Thanks, @nmccready!)

Commits

The new version differs by 19 commits.

• b4d00bd 0.16.0 (#44)
• 4748898 feat: allow load options (#35)
• 91a34aa Merge pull request #42 from googleapis/greenkeeper/nyc-12.0.1
• fca6f75 Update package.json
• f0473ad chore(package): update nyc to version 12.0.1
• 0575631 chore: lock files maintenance (#41)
• 5f38e7f chore: lock files maintenance (#38)
• d077e0b chore: test on node10 (#37)
• 7855cca chore: lock files maintenance (#36)
• e554818 Merge pull request #32 from googleapis/greenkeeper/sinon-5.0.0
• 0ecbb5e Update package locks
• 838e2d1 chore(package): update sinon to version 5.0.0
• fb18058 chore: workaround for repo-tools EPERM (#33)
• cf5968e chore: setup nighty build in CircleCI (#31)
• c4c973a chore(package): update proxyquire to version 2.0.0 (#30)

There are 19 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[googlebot]

So there's good news and bad news.

👍 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.

😕 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 the commit author(s) and merge this pull request when appropriate.

[codecov]

Codecov Report

Merging #139 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #139   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           8      8           
  Lines         867    867           
=====================================
  Hits          867    867

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c976e8...d40a6de. Read the comment docs.