-
Notifications
You must be signed in to change notification settings - Fork 511
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
Update go build version to something current #532
Comments
ping @alecholmez @snowp @kyessenov |
grprc-go depends on go-control-plane and Go 1.14, so it would be less disruptive to only bump up to 1.14. |
This works for me let's bump it up |
Ping @markdroth for gRPC perspective. IIUC, bumping the go-control-plane version pasts Go 1.14 (which is where gRPC is) would have no immediate ill effects. The risk would be that if go-control-plane starts to use > 1.14 language features, that would not build in a Go 1.14 program (and people using gRPC might get a nasty surprise). |
Update the Go version directive to 1.16 since that is currently the oldest supported go release. This fixes envoyproxy#532. Signed-off-by: James Peach <jpeach@apache.org>
@dfawley is the right person to weigh in on grpc-go issues. |
grpc-go also mentions it should be used with probably worth bumping up the module requirement there to ensure that statement is correct as well |
Update the Go version directive to 1.16 since that is currently the oldest supported go release. This fixes #532. Signed-off-by: James Peach <jpeach@apache.org>
sent grpc/grpc-go#5102 as well to start a discussion |
In #272,
go.mod
was downgraded to Go 1.11. While that was an unsupported release at the time, it's still unsupported. Per the Go release policy, the last 2 major releases are supported, which at time of writing puts us on 1.17 or 1.16.The downgrade was done to support grpcurl, which I guess ended up taking a go-control-plane dependency via gRPC. grpcurl is on Go 1.15 now, so that seems like a safe minimum. My preference would still be to use oldest supported Go release.
The text was updated successfully, but these errors were encountered: