Description
The grpctransport SDK module requires Go 1.24 because google.golang.org/grpc itself pins that version. This pushes consumers stuck on Go 1.22 to either upgrade their toolchain or use the core SDK (configclient, configwatcher, adminclient) with a custom transport.
If demand warrants it, we'd build a grpctransport-legacy (or similar) module that pins an older grpc version (~v1.60–v1.65 era) compatible with Go 1.22.
Trade-offs of a legacy variant:
- Older grpc = missing ~2 years of bug/security fixes
- Extra module to maintain + test in CI
- Consumers must pick between new features vs. old toolchain
How to signal demand
- React with 👍 if you need this
- Comment with your Go version constraint (why Go 1.22, which grpc features you don't need)
Acceptance criteria
Description
The
grpctransportSDK module requires Go 1.24 becausegoogle.golang.org/grpcitself pins that version. This pushes consumers stuck on Go 1.22 to either upgrade their toolchain or use the core SDK (configclient,configwatcher,adminclient) with a custom transport.If demand warrants it, we'd build a
grpctransport-legacy(or similar) module that pins an older grpc version (~v1.60–v1.65 era) compatible with Go 1.22.Trade-offs of a legacy variant:
How to signal demand
Acceptance criteria