NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central, #743 by repository stars
gRPC: Cronet Android
Latest stable
1.85.1
Last release 1 months ago
21 Oct 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
145 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
core: Fix CompositeChannelCredentials to no longer use CallCredentials for OOB channels. OOB channels are available for load balancing policies to use
GRPC_XDS_EXPERIMENTAL_NEW_SERVER_API=true where gRPC would request non-existent resourcesThe previous APIs are stable so will not be removed, but are expected to be deprecated in the future. Since these new APIs will be widely used, we enc…
This release has a severe bug when using CompositeChannelCredentials that predominantly impacts googleapis.com (#7643). You may be impacted in the future even if not impacted today. If you contact googleapis.com, please use 1.34.1 instead.
io.grpc.ForwardingServerBuilder (#7633)usePlaintext() and useTransportSecurity() methods on the channel and server builders. The previous APIs are stable so will not be removed, but are expected to be deprecated in the future. Since these new APIs will be widely used, we encourage users to try the APIs out and report any problems experienced so they can be corrected before the APIs become stable (#7294, #7601)StatusRuntimeException: INTERNAL: http2 exception with a cause similar to Http2Exception$StreamException: Cannot create stream 222691 greater than Last-Stream-ID 222689 from GOAWAY. This was mainly observed when a C core-based gRPC server shut down. (#7501)ServerCall#close (#7580)@attila123 @erikjoh @jbdeboer @ST-DDT @sullis @susinmotion
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Fix builders ABI backward compatibility broken in v1.33.0, see #7552
io.grpc.netty.NettyServerBuilder reverted to extend internal class io.grpc.internal.AbstractServerImplBuilderio.grpc.netty.NettyChannelBuilder reverted to extend internal class io.grpc.internal.AbstractManagedChannelImplBuilderio.grpc.okhttp.OkhttpChannelBuilder reverted to extend internal class io.grpc.internal.AbstractManagedChannelImplBuilderThe class io.grpc.inprocess.InProcessChannelBuilder reverted to extend internal class io.grpc.internal.AbstractManagedChannelImplBuilderio.grpc.cronet.CronetChannelBuilder reverted to extend internal class io.grpc.internal.AbstractManagedChannelImplBuilderForwardingServerBuilder reverted until the permanent fix of the issue with ABI compatibility of delegating classesStatusRuntimeException: INTERNAL: http2 exception with a cause similar to Http2Exception$StreamException: Cannot create stream 222691 greater than Last-Stream-ID 222689 from GOAWAY. This was mainly observed when a C core-based gRPC server shut down.api, core: delete io.grpc.LoadBalancer.loadBalancingConfig attribute (#7440). The attribute was deprecated in v1.27.0, now it is completely deleted.
This release broke ABI in a non-planned way for NettyServerBuilder, NettyChannelBuilder, and similar. See https://github.com/grpc/grpc-java/issues/7552. If you are impacted, please use an earlier version until v1.33.1 is available. A future ABI breakage may be necessary, but will be communicated explicitly at that time.
io.grpc.netty.NettyServerBuilder is no longer a subclass of the internal class io.grpc.internal.AbstractServerImplBuilderio.grpc.netty.NettyChannelBuilder is no longer a subclass of the internal class io.grpc.internal.AbstractManagedChannelImplBuilderio.grpc.okhttp.OkhttpChannelBuilder is no longer a subclass of the internal class io.grpc.internal.AbstractManagedChannelImplBuilderThe class io.grpc.inprocess.InProcessChannelBuilder is no longer a subclass of the internal class io.grpc.internal.AbstractManagedChannelImplBuilderio.grpc.cronet.CronetChannelBuilder is no longer a subclass of the internal class io.grpc.internal.AbstractManagedChannelImplBuilderStatusRuntimeException: CANCELLED from onNext() for streaming responses. Previously the exception was also thrown from onNext() for unary responses and from onComplete(), which didn’t help the server avoid unnecessary processingonMessage() after onClose())GRPC_EXPERIMENTAL_AUTOFLOWCONTROL=false introduced later. The symptom was a GOAWAY with “too_many_pings” without an aggressive keepalive configured. The environment variable is still available, but will be removed in the future{"type":"insecure"}” for plaintext (#7396)repositories.bzl, in favor of maven_install. v1.27.0 introduced support for maven_install and encouraged users to migrate. See examples/WORKSPACE for an example. maven_install dramatically reduces the boilerplate for maven dependencies and properly handles transitive dependencies and version selection. gRPC is not yet using the @maven workspace, so it is still possible to use other dependency tools.@codeblooded Benjamin Reed @kiwi1969 Russell Shaw @pkern Philipp Kern
xds: Fixed JSON number types in internally generated service config for header matching (more specifically, range matching for numerical headers) (#78
netty: TCP close during TLS handshake should be UNAVAILABLE, not UNKNOWN
GRPC_EXPERIMENTAL_AUTOFLOWCONTROL=false introduced later. The symptom was a GOAWAY with “too_many_pings” without an aggressive keepalive configured. The environment variable is still available, but will be removed in the futureapi: Removed deprecated method ChannelBuilder.blockingExecutor() (#7242). There should not be any users as it was deprecated the first release it was…
ChannelBuilder.blockingExecutor() (#7242). There should not be any users as it was deprecated the first release it was available and was renamed offloadExecutor().GRPC_EXPERIMENTAL_AUTOFLOWCONTROL=false will now disable the BDP monitoring introduced in v1.30.0. This is intended to help diagnose a “too_many_pings” compatibility issue and will be removed once it is resolved. If you need to use the variable, please file an issue@susinmotion @trustin @wanyingd1996
xds: Fixed JSON number types in internally generated service config for header matching (more specifically, range matching for numerical headers) (#78
netty: The environment variable GRPC_EXPERIMENTAL_AUTOFLOWCONTROL=false will now disable the BDP monitoring introduced in v1.30.0. This is intended to
GRPC_EXPERIMENTAL_AUTOFLOWCONTROL=false will now disable the BDP monitoring introduced in v1.30.0. This is intended to help diagnose a “too_many_pings” compatibility issue and will be removed once it is resolved. If you need to use the variable, please file an issueapi: ManagedChannelBuilder.nameResolverFactory is now marked deprecated. It has long been our plan to remove the function, but was not communicated. M…
ManagedChannelBuilder.nameResolverFactory is now marked deprecated. It has long been our plan to remove the function, but was not communicated. Most usages should be able to globally register via the SPI mechanism or NameResolverRegistry.register(). There is a plan to add a method to ManagedChannelBuilder to specify the default target scheme for the channel. If your use-case is not covered, please inform us on #7133LoadBalancer.Helper.createResolvingOobChannelBuilder(). It is similar to LoadBalancer.Helper.createResolvingOobChannel() except allows configuring the channel (#7136)@alexanderscott @AnarSultanov @cindyxue @d-reidenbach @elharo @gsharma @reggiemcdonald
xds: disable code for a future xds feature
all: remove grpc-rls from grpc-all dependencies (#7118). grpc-rls is not intended to be published yet, projects depending on grpc-all gets a "failed t
There may still be some tweaks to the API, so disableAutoInboundFlowControl() is not yet deprecated.
Note: gRPC-Java no longer exposes many transitive dependencies as "compile" dependencies, but instead specifies them as "runtime" dependencies. Consuming projects using these dependencies directly will need to explicitly add the dependencies to their compile-time classpath.
NettyChannelBuilder#flowControlWindow or NettyServerBuilder#flowControlWindow. Existing flowControlWindow users need to use initialFlowWindowSize to enable BDP. The default initial window size has remained unchanged, so most users should not see a performance difference. In the future we plan to reduce the default size, which may briefly (up to 4 RTT) slow down new connections as they determine an appropriate BDP.xds. This is the stable version of the scheme xds-experimental that was introduced in v1.28.0. xds-experimental scheme will be removed in subsequent releases so you must switch to xds scheme instead. xds scheme is a client side implementation of xDSv2 APIs. This allows a gRPC client written in Java to receive configuration from an xDSv2 API compatible server and use that configuration to load balance RPCs. In this release, only the virtual host matching, default path (“” or “/”) matching and cluster route action are supported. The features supported in a given release are documented here.ClientCallStreamObserver.disableAutoRequestWithInitial(int) and ServerCallStreamObserver.disableAutoRequest() that disables all automatic inbound flow-control requests. These methods are intended to replace the existing CallStreamObserver.disableAutoInboundFlowControl(). There may still be some tweaks to the API, so disableAutoInboundFlowControl() is not yet deprecated.InprocessChannelBuilder.propagateCauseWithStatus(true) to propagate exceptions from the server within status.getCause() (#6968). This is intended for unit tests to ease debugging test failures.NettyServerBuilder to allow passing channel options for the boss ELG.org.apache.tomcat:annotations-api for the @Generated annotation instead of javax.annotation:javax.annotation-api, as it has a more appropriate license@agasparovic-sabre @AgentK20 @apolcyn @asdf2014 @ashithasantosh @chalin @bogdandrutu @DRayX @hojongs @Nextproc @plaflamme @reggiemcdonald @RiyaTyagi
core, grpclb: change policy selection strategy for Grpclb policy (move logic of querying SRV into Grpclb's own resolver) (#6723). System property io.g
io.grpc.internal.DnsNameResolverProvider.enable_grpclb is eliminated, grpc-grpclb dependency implicitly enables querying SRV records since v1.24.2ServerInterceptors.useInputStreamMessages() now preserves the KnownLength interface when wrapping InputStream (#6852). This should prevent certain optimizations from being disabled when using useInputStreamMessagesServerInterceptors.useInputStreamMessages() and useMarshalledMessages() now preserve the SchemaDescriptor, so the methods are now compatible with the reflection service (#6851)-PskipAndroid=false (default) includes building grpc-android module, which requires Android SDK@chrisschek @elharo Elliotte Rusty Harold @herbyderby Chris Nokleberg @markb74 @ST-DDT
This patch is mainly for the experimental xDS-related features.
This patch is mainly for the experimental xDS-related features.
LoadBalancer developers should use parsed config(loadBalancingPolicyConfig) in ResolvedAddresses instead of deprecated attribute io.grpc.LoadBalancer.…
LoadBalancerProvider#parseLoadBalancingPolicyConfig. LoadBalancer developers should use parsed config(loadBalancingPolicyConfig) in ResolvedAddresses instead of deprecated attribute io.grpc.LoadBalancer.ATTR_LOAD_BALANCING_CONFIG.ManagedChannelBuilder#defaultServiceConfig or ManagedChannelBuilder#defaultLoadBalancingPolicy).OkHttpChannelBuilder.flowControlWindow(), who seem to be few since this bug was not reported sooner@chrisschek @cushon Liam Miller-Cushon @elharo Elliotte Rusty Harold @gfelbing Georg Welzel @hatahet Ziad Hatahet @leventov Roman Leventov @sourabhsparkala Sourabh Sarvotham Parkala @ZhenLian Zhen Lian
grpclb: grpclb can handle empty address from LoadBalancer instead of throwing exception
alts: Fix using the wrong way of checking if Conscrypt is available
*Bazel users should migrate to maven_install. Please open an issue to report problems migrating to maven_install.*
Bazel users should migrate to maven_install. Please open an issue to report problems migrating to maven_install.
grpc-core. A grpc-census artifact now exists to provide interceptor/stream tracer factory that applies census stats/tracing features. For users not using gRPC’s integration of census, nothing should be affected. Users who want census integration need to add grpc-census artifact to runtime classpath (#6577)animal-sniffer-annotations to 1.18 (#6488)error_prone_annotations to 2.3.4 (#6574)google-auth-library-credentials and google-auth-library-oauth2-http to 0.19.0 (#6537)proto-google-common-protos to 1.17.0 (#6572)existing_rule() check (#6553). If you are passing any arguments to grpc_java_repositories() within your WORKSPACE, you will need to remove those arguments and make sure you run grpc_java_repositories() after defining any overridden repositoriesexamples/WORKSPACE for typical usage. grpc-java still supports the jvm_maven_import_external()-based loading only to ease migration. grpc-java will drop usages of jvm_maven_import_external() in the future-Dio.grpc.netty.useCustomAllocator=true by default (#6528). This causes grpc to use a different Netty allocator by default which is configured to allocate in smaller chunks which may reduce memory usage by 8x on lightly loaded systems. Performance benchmarks show virtually no change with any potential slowdowns hidden in the noise (~1%). See also #6407. If you notice problems, set the property to false and file an issueAuthorizationUtil utility library for verifying a client is a particular account (#6529)NettyServerBuilder.addListenAddress()) may deadlock (bug #6641). This has been the case since its introductionbazel: Use https to download from Maven Central
api: the deprecated API ManagedChannelBuilder.usePlaintext(boolean) is removed (#1772, #6440).
protobuf-java to 3.11.0.protobuf-javalite to 3.11.0. This brings lite in-line with full protobuf. Be aware that the Maven artifact name changed for Protobuf lite. The dependency is now com.google.protobuf:protobuf-javalite instead of com.google.protobuf:protobuf-litegson to 2.8.6google-auth-library-credentials and google-auth-library-oauth2-http to 0.18.0 (#6360)IOExceptions are logged as FINE level1.19.0) is now published againAbstractStub to indicate stub type (AbstractAsyncStub, AbstractFutureStub, AbstractFutureStub)ManagedChannelBuilder.usePlaintext(boolean) is removed (#1772, #6440).Note that grpclb is still experimental and deprecated. In particular, we plan to change grpclb policy selection which together with this change provid…
netty to 4.1.42error_prone_annotations to 2.3.3perfmark to 0.19.0guava to 28.1gson to 2.8.5protobuf to 3.10.0truth to 1.0ClientCall.Listener.onClose never called when the call is interrupted” (#6255)ComputeEngineChannelBuilder class signature (#6367)protoc-gen-grpc-java (#6247)TE: trailers header after checking Content-Type. This prevents confusing warnings when a non-grpc client contacts a grpc serverrepositories.bzl for maven_install override_targets; io.grpc:grpc-core was pointing to a non-existent target nameMethodDescriptor’s safe and idempotent methods are now considered stable and set appropriately by the generated code when the proto contains the RPC option option idempotency_level = NO_SIDE_EFFECTS; or option idempotency_level = IDEMPOTENT;. grpc-java is not using these values directly, but interceptors are free to observe themStatusProto.fromStatusAndTrailers fall-back to status if trailers are not available (#6278). Previously it returned nullgrpc_java_repositories() that protobuf_deps() providesManageChannelBuilder.usePlaintext() (with no argument) is now stabilized.--incompatible_load_cc_rules_from_bzl and --incompatible_load_proto_rules_from_bzlEquivalentAddressGroup.ATTR_AUTHORITY_OVERRIDE which allows NameResolvers to specify different names for different backends within one Channel which may be especially useful for certain TLS deployments (#6126). Note that NameResolvers must receive the authority names from a trusted source (e.g., local file, remote server with TLS)EquivalentAddressGroup Attributes in RoundRobinLoadBalancer. This allows NameResolvers to set attributes like ATTR_AUTHORITY_OVERRIDE with round robinManagedChannelBuilder.offloadExecutor() for expensive or blocking operations like DNS resolution. Previously an internal executor was used that couldn’t be overridden. The executor is also passed to NameResolvers via Args.getOffloadExecutor()io.grpc.grpclb that has SRV record lookup enabled by default (#6298). This allows using grpclb without the -Dio.grpc.internal.DnsNameResolverProvider.enable_grpclb=true system property. Note that grpclb is still experimental and deprecated. In particular, we plan to change grpclb policy selection which together with this change provides a path forward for grpclb to function without custom support in grpc-core; see gRFC A26Note that grpclb is still experimental and deprecated. In particular, we plan to change grpclb policy selection which together with this change provid…
perfmark to 0.19.0error_prone_annotations to 2.3.3ComputeEngineChannelBuilder class signature (#6381)io.grpc.grpclb that has SRV record lookup enabled by default (#6298). This allows using grpclb without the -Dio.grpc.internal.DnsNameResolverProvider.enable_grpclb=true system property. Note that grpclb is still experimental and deprecated. In particular, we plan to change grpclb policy selection which together with this change provides a path forward for grpclb to function without custom support in grpc-core; see gRFC A26Note that grpclb is still experimental and deprecated. In particular, we plan to change grpclb policy selection which together with this change provid…
This release resolves proxy hang issue during initial protocol negotiation, users using proxy should upgrade.
ADDED: please upgrade to 1.24.2 or 1.25.0, see known issues for more details.
1.24.2 or 1.25.0.error_prone_annotations version requirement when building the application (#6217). Adding perkmark 0.19.0 (io.perfmark:perfmark-api:0.19.0) to dependency can workaround this issue.io.grpc.grpclb that has SRV record lookup enabled by default (#6298). This allows using grpclb without the -Dio.grpc.internal.DnsNameResolverProvider.enable_grpclb=true system property. Note that grpclb is still experimental and deprecated. In particular, we plan to change grpclb policy selection which together with this change provides a path forward for grpclb to function without custom support in grpc-core; see gRFC A26~ correction: didn't made the cut, please use 1.25.0 or 1.24.2.The deprecated API ManagedChannelBuilder.usePlaintext(boolean skipNegotiation) will be removed in the next release. If you are still using it, please…
One column per quarter.