Due to grpc-go team makes incompatible changes to the gRPC service generator could you please follow semver-tags for main package? If my module used google.golang.org/grpc v1.31.0 I will be very appreciated to know how I can install appropriate proto-gen-go-grpc version which not break my code?
Today doesn't work:
> go get -u google.golang.org/grpc/cmd/[email protected]
go get google.golang.org/grpc/cmd/[email protected]: module google.golang.org/[email protected] found, but does not contain package google.golang.org/grpc/cmd/protoc-gen-go-grpc
I really hate the situation, when I cannot determine which version of this generator will be installed and what will happen after!
protoc-gen-go-grpc is in its own, new module and has never been released. It is still v0. Backward-incompatible changes are to be expected.
If you want the old service registration pattern, you need to use the legacy codegen tool which is stable but deprecated (i.e. it will not receive any updates). E.g.:
go install github.com/golang/protobuf/protoc-gen-go
protoc --go_out=plugins=grpc:.
@dfawley go install brings latest plugin version from master in my case.
Only get -u google.golang.org/grpc/cmd/protoc-gen-go-grpc@cee815d helps.
Most helpful comment
@dfawley
go installbrings latest plugin version from master in my case.Only
get -u google.golang.org/grpc/cmd/protoc-gen-go-grpc@cee815dhelps.