-
Notifications
You must be signed in to change notification settings - Fork 227
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
fix: update minimum gax version to 2.7.0 to fix recent protobuf errors #1085
Conversation
… and commit those changes
Pulling in @alexander-fenster to make sure this makes sense. |
Codecov Report
@@ Coverage Diff @@
## master #1085 +/- ##
=======================================
Coverage 97.78% 97.78%
=======================================
Files 25 25
Lines 11067 11067
Branches 546 575 +29
=======================================
Hits 10822 10822
Misses 241 241
Partials 4 4 Continue to review full report at Codecov.
|
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.
This seems right to me, I agree that getting @alexander-fenster's feedback would be good, let's not break folks twice.
To fix recent protobuf errors based on googleapis/nodejs-pubsub#1085.
To fix recent protobuf errors based on googleapis/nodejs-pubsub#1085. Fixes googleapis#1209
To fix recent protobuf errors based on googleapis/nodejs-pubsub#1085. Fixes #1209
Source-Link: googleapis/synthtool@4dfd20a Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:2d850512335d7adca3a4b08e02f8e63192978aea88c042dacb3e382aa996ae7c
If a user has an old version of gax installed and then updates Pub/Sub (specifically 2.4.0 after a synthtool update), it will cause object resolution failures, and possibly other problems. This bumps the minimum gax version to the latest release to take care of that mismatch.
Fixes: #1082