opened
chiragvels
username_0
Hi,

I would suggest to define/add gRPC and protobuf version on composer.json that is compatible with release of the new version of the Library.

So that we can prevent any stability related issues due to changes done on gRPC and Protobuf versions.

Thanks,
Define gRPC and Protobuf verison compatible with Released version of Library
issue
created
fiboknacky
username_1
Thanks for suggestion, but this library needs to rely on [gax-php](https://github.com/googleapis/gax-php/blob/master/composer.json#L12), which in turn has its own dependencies on gRPC and protobuf.
I'm afraid that, like in the past, if we add the dependencies on gRPC and protobuf directly here but cannot update the versions at around the same time as those of `gax-php`, it will cause a conflict for people who specify dependency on both this library and `gax-php` directly.

We're pretty in touch with the teams managing `gax-php`, protobuf and gRPC, and coordinating with those teams to ensure the dependencies are always updated in the future.
Pierrick, do you have any other updates or opinions on this?
comment
created
PierrickVoulet
username_2
@username_0 thanks for opening this issue.

IMO there is no perfect solution, only a trade-off between flexibility and stability. Relying on `gax-php` dependency rules makes things simple and flexible (useful for most environments) but it can sometimes makes things unstable (especially problematic for production environments). I think we should keep it as-is but plan mitigation action items:

* Highlight in our documentation the stability benefit of specifying the versions of the Protobuf and gRPC dependencies and how it can be done in a project that depends on our library. We could recommend to do so for production environments.
* Add integration testing on our end to raise issues to Protobuf and gRPC before new releases.
comment
created
PierrickVoulet
username_2
I flagged this issue as enhancement: documentation could be improved to address this.
comment
created
chiragvels
username_0
Thanks,
comment