-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Please make a new release! #963
Comments
What error are you seeing? I was under the impression the last error was fixed with the latest release. |
Also, there's no reason protoc shouldn't work in go modules mode that I know of, this repo uses modules and protoc successfully. I would recommend that you version the generator together with your runtime dependency. With Go modules that is done via tool dependencies: https://github.com/golang/go/wiki/Modules#how-can-i-track-tool-dependencies-for-a-module |
@johanbrandhorst The |
This is included in the |
@johanbrandhorst You're right. |
I've just released 1.9.3, FYI. |
When generating our source codes using
protoc
, we always install the latest version ofgrpc-gateway
sinceprotoc
does not work in Go modules mode.When importing generated codes in our repos, we use Go modules and we use the latest release of
grpc-gateway
.Problem:
Currently,
grpc-gateway
has a breaking change onmaster
branch which is not yet released. So, we cannot fix it our repos unless we import thegrpc-gateway
module frommaster
instead of semantically versioned releases.The text was updated successfully, but these errors were encountered: