Repository navigation
feat(core): generate connect-go v2 service stubs in protocol/go - #4237
alkalescent wants to merge 1 commit into
Conversation
buf.gen.yaml also runs the connect-go v2 plugin with the connectv2 package suffix, so each service gets a v2 stub package next to its v1 stub package. connect-go v2 requires Go 1.26, so protocol/go and go.work move to Go 1.26. Signed-off-by: Krish Suchak <suchak.krish@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
|
Benchmark results, click to expandBulk Benchmark Results
TDF3 Benchmark Results
|
|
|
||
| require ( | ||
| buf.build/gen/go/bufbuild/protovalidate/protocolbuffers/go v1.36.11-20260709200747-435963d16310.1 | ||
| connectrpc.com/connect v1.20.0 |
There was a problem hiding this comment.
Yes, we need both deps as we generate both v1 and v2 bindings until the migration is complete. Servers will move to v2 while clients can stay on v1.
| @@ -1,6 +1,6 @@ | |||
| go 1.25.5 | |||
| go 1.26.0 | |||
There was a problem hiding this comment.
if were updating the go work should we update the go ver of the rest of the modules as well?
Proposed Changes
buf.gen.yamlalso runs the connect-go v2 plugin (buf.build/connectrpc/go:v2.0.1) withpackage_suffix=connectv2. Each service gets a v2 stub package next to its v1 stub package, for examplepolicy/attributes/attributesconnectv2next topolicy/attributes/attributesconnect. The messages and v1 stubs do not change.protocol/go.protocol/goandgo.workmove to Go 1.26. Modules that update to thisprotocol/gorelease need Go 1.26.Checklist
Testing Instructions
Summary by CodeRabbit