grpc/protobuf: manually force the latest version

[Gounlaf]

Hi 👋,

This commit follows #633 ; protobuf and grpc are both impacted

[mlocati]

Could you amend the commit, by adding a new line containing Test: grpc, protobuf (as described in README)?

Also: this implies that we have to update the script every time a new version of grpc and protobuf is published... This is something that I'm reclutant to do (maintaining this project it's already rather time consuming)

[Gounlaf]

Could you amend the commit, by adding a new line containing Test: grpc, protobuf (as described in README)?

Done

Also: this implies that we have to update the script every time a new version of grpc and protobuf is published... This is something that I'm reclutant to do (maintaining this project it's already rather time consuming)

Yes... What I understand is there is no guarantee that protoc or grpc release will be published in a "linear" way, and we can't rely on PECL to give the latest version "correctly" (following semver)

• I can update the script every time (not necessary in the same time) via PR; If it's not done here, I will have to do it on Docker images that consume your script... so I would rather do it here for everyone :)
• I can try to create a "github action" that will update the script automatically by watching grpc/protobuf release.

[mlocati]

there is no guarantee that protoc or grpc release will be published in a "linear" way

The same is valid for any other package published on PECL.

The best solution would be what's described at protocolbuffers/protobuf#10619 (comment) (and I hope one day PECL will be able to mark a version as the last one, even if it has been uploaded before other versions).

[mlocati]

@Gounlaf Please remark that, thanks to php/web-pecl#92, we don't need to manually specify the versions of grpc/protobuf anymore (so, I don't have to do stuff like #728, #741, #744, #746, #747, #749, #756, #759, #773, #782, #785, #788, #793 anymore) - see #798