-
Notifications
You must be signed in to change notification settings - Fork 435
Update vendored gRPC-core to v1.23.0 #563
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
Conversation
MrMage
left a comment
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.
Upon a cursory look, this looks good. Were there any manual changes besides the redundant include that you needed to do, so we can document them?
|
I'd also like for @rebello95 to take a look before merging this. |
Nope. 9d8ab80 is the result of |
|
@tsabirgaliev thank you! Happy to merge this once @rebello95 approves as well. |
|
This implies it's safe to update the dependency on |
|
@Westacular is Pods the only package spec shipped here? I’m afraid I’m not enough competent to cover them all :) |
|
Right, the Podspec also needs to be updated and the Carthage project generation script re-run as well.
… On 29. Aug 2019, at 20:01, Tair Sabirgaliev ***@***.***> wrote:
@Westacular is Pods the only package spec shipped here? I’m afraid I’m not enough competent to cover them all :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
We should have documentation somewhere on all the steps to do when updating the vendor gRPC. Or just look at the previous update PR :-)
… On 29. Aug 2019, at 20:01, Tair Sabirgaliev ***@***.***> wrote:
@Westacular is Pods the only package spec shipped here? I’m afraid I’m not enough competent to cover them all :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@MrMage haha, good catch :) it is exactly what I did. I even copy-pasted the commit messages. |
MrMage
left a comment
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 think we should indeed update the Podspec and the Carthage project in this PR as well.
|
@MrMage do we need to also bump the grpc-swift version in Podspec? |
No, one of the team will do that when releasing the next version of Swift gRPC. |
|
@MrMage I'm sorry, I don't get how to update the Carthage project. Is it just |
Yes, that should be it. |
|
Thank you for the changes, @tsabirgaliev! Once the next release is cut, the library will officially use gRPC-Core 1.23. Until then, you can already use it by using the |
|
Thanks for doing this! Sorry I was unable to review - was OOO last week. |
Motivation: gRPC v1.23.0 enables CFStream by default on iOS. This feature potentially can solve connectivity problems (#337)