Update pubsub to 2.3.0 #16038
Merged
Update pubsub to 2.3.0 #16038
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update pubsub to ~> 2.3 and some other dependencies. In particular I
had to update gapic manually in order to solve a conflict, by issuing
the following:
bundle update gapic-common
A more aggressive update can be performed with `bundle update` (no
extra gem) but did not want to run the risk (it can be done in a
latter PR).
rafatower
deleted the
chore/ch128685/update-pubsub-ruby-clients-to-2-3-0
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update pubsub to ~> 2.3 and some other dependencies. In particular I
had to update
gapicmanually in order to solve a conflict, by issuingthe following:
A more aggressive update can be performed with
bundle update(noextra gem) but did not want to run the risk (it can be done in a
latter PR).
Related to CartoDB/cartodb-common#36 that should be merged and released first (after passing the tests), then make this point to the next tagged version.