NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central, #727 by repository stars
gRPC: GRPCLB LoadBalancer plugin
Latest stable
1.85.1
Last release 28 days 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
11 years old
197 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
CallOptions.withAffinity is now deprecated in favor of withOption and will be removed in the next release
io.grpc.protobuf.StatusProto for working with com.google.rpc.Status, which can include additional error detailsStreamTracers on client- and server-side. These can be used by tracing frameworks and LoadBalancers to be notified of relevant RPC events and details. OkHttp and Netty support the tracers, but InProcess does notMethodDescriptor.Builder is now non-experimentalLoadBalancer2 to LoadBalancer was removed as plannedLoadBalancer.SubchannelPicker.pickSubchannel(Attributes, Metadata) was deleted as planned in favor of the more extensible LoadBalancer.SubchannelPicker.pickSubchannel(PickSubchannelArgs)CallOptions.withAffinity is now deprecated in favor of withOption and will be removed in the next releaseNettyChannelBuilder. and OkHttpChannelBuilder.enableKeepAlive is now deprecated in favor of keepAliveTime and keepAliveTimeout and will be removed in the next releaseResolvedServerInfoGroup and ResolvedServerInfo are deprecated and are planned for deletion in the next releaseYour coding agent can read these notes before it upgrades. Set up the MCP server →
The new Load Balancer API (and ManagedChannelImpl) is now default; the previous one is removed
This is a patch release to the 1.1 gRPC branch that fixes two minor issues:
This is a patch release to the 1.1 gRPC branch that fixes two minor issues:
grpc-all artifact on the yet to be released grpc-thrift artifactThe grpc-io mailing list was notified of our intentions and reasoning. This is a breaking change but is not expected to impact production code. If a t…
I am pleased to announce availability of gRPC Java 1.1.1, the next minor release of gRPC. This includes several months of changes made since 1.0.3. There are many bug fixes, API improvements, and performance changes in this release.
grpc-context. It can (and will) be used for implementing cross RPC state, such as for stats and tracing.Mockito.when(service.bindService()).thenCallRealMethod();. If this change causes you pain, please file an issue and we may revisit it.examples/ directory.Note that all classes marked @ExperimentalApi and @Internal aren't guaranteed to be API stable, and may be changed without notice. Classes and methods marked @Deprecated should be avoided and may be removed in a later release. Of note is ClientAuthInterceptor, which should be avoided in favor of MoreCallCredentials.
The v1.0.3 release has a small bugfix and experimental support for forward proxies. Only users of InProcess transport in tests or users wanting to tes
The v1.0.3 release has a small bugfix and experimental support for forward proxies. Only users of InProcess transport in tests or users wanting to test the forward proxy support benefit from the update.
GRPC_PROXY_EXP environment variable and set to a host:port-formatted string. Error handling is known to be weak when negotiating with the proxy; most proxy failures will result in a generic error. Errors after negotiation completes are unaffected.The v1.0.2 release is a bug fix release with no new features. The following specific fixes were backported from the master branch:
The v1.0.2 release is a bug fix release with no new features. The following specific fixes were backported from the master branch:
Moved io.grpc.Context and io.grpc.Deadline from grpc-core to its own artifact, grpc-context. This is to allow wider usage of the API and avoid circula
io.grpc.Context and io.grpc.Deadline from grpc-core to its own artifact, grpc-context. This is to allow wider usage of the API and avoid circular dependencies. grpc-core depends on the new artifact. (#2226)Errors could end up being wrapped in RuntimeException (#2131)TransportSet (#2258)grpc-protobuf-lite now depends on protobuf-lite. Since grpc-protobuf depends on grpc-protobuf-lite, grpc-protobuf explicitly excludes the protobuf-lit
Generated interfaces and methods that were deprecated in v0.15.0 are now removed. To ease migration, the grpc protoc plugin supports the option enable…
enable_deprecated=true which will re-enable the old generated APIs. This option will be removed in a later release.
directExecutor() for both the client and server. Some tests may need to use a ClientInterceptor to verify the CallOptions. We plan to improve convenience utilities over time; please file a bug for testing issues or suggested utilities.ManagedChannelBuilder.maxMessageSize() and ServerBuilder.maxMessageSize() can override the default. Larger sizes are not a problem for grpc, but applications should be aware when they may receive large messages.ManagedChannelBuilder.idleTimeout(). IDLE disconnects the TCP connection and shuts down the name resolver and load balancer. This is generally useful for reducing resources, but can also be used on Android to avoid broken TCP connections on bad networks and "avoid" timeouts of NATs and load balancers.OkHttpChannelBuilder.enableKeepAlive(). Keepalive uses HTTP/2 PINGs while RPCs are in progress to monitor the TCP connection and signal activity to NATs and load balancers. Keepalive does nothing if no RPCs are in progress, thus is primarily useful when for long-lived streaming RPCs. This implementation preempts the design of keepalive being finalized, but was important enough for mobile networks to have something available sooner. This can be used on Android to detect broken TCP connections on bad networks and reset timeouts of NATs and load balancers.ServiceLoader on the platform. If your application never calls Class.getResource(), this will reduce memory on some Android versions and speed construction of your first ManagedChannel. This also simplifies the necessary ProGuard configuration. General-purpose 3rd-party providers for NameResolver and ManagedChannel that may be used on Android should request to be added to the hard-coded list.ClientCall.cancel(String, Throwable) is now a required method and will log a warning when called with neither a message nor cause. This completes the migration from ClientCall.cancel(void) which was very difficult to debug where cancel was called.StatusRuntimeExceptions for blocking unary calls should now include trailers.…and grpc-interop-testing. APIs marked @Deprecated in this release are not covered. Mocking frameworks purposefully break API assumptions, so we can't…
APIs and codegen are guaranteed stable, excluding APIs marked with @ExperimentalApi or @Internal, APIs within an internal package, and utilities like grpc-benchmarks and grpc-interop-testing. APIs marked @Deprecated in this release are not covered. Mocking frameworks purposefully break API assumptions, so we can't guarantee stability with them.
ForkJoinPool, as the executor is the bottleneck for high CPU (16+ core), high QPS benchmarks. On smaller workloads using normal ThreadPoolExecutor is fastergenerated AbstractService class and interfaces are now deprecated in favor of ServiceImplBase
Update Netty to v4.1.1.Final, which is the first stable release we've released with. gRPC-java v0.14.0 was already compatible with Netty v4.1.1. This
It is now possible to use JSON-encoded protobufs.
interceptForward().ExtensionRegistry.CallOptions now uses Attributes for affinity routing.CallStreamObserver and ServerCallStreamObserver as specialized Stub observers.CallOptions and stubs now uses Deadline instead of a long of nanoseconds.TransportSets.Updates to Netty 4.1.0.CR3, which allows using netty-tcnative-boringssl-static 1.1.33.Fork14 which does not give a warning about executable stacks. Al
This release contains a single fix (103d3d1) to avoid an out-of-order headers bug impacting Netty-4.1.0.CR1. The bug manifests when starting multiple
This release contains a single fix (103d3d1) to avoid an out-of-order headers bug impacting Netty-4.1.0.CR1. The bug manifests when starting multiple RPCs simultaneously as an opaque error before receiving any responses or the RPC never receiving any response or status. If an RPC was successful then it was not impacted
Support netty-tcnative-boringssl-static, which does not require OpenSSL to be installed. See SECURITY.md. The current build works but omits a warning;
New and Notable:
Context.Key now uses instance equality, so if you reduce visibility to your Key you are guaranteed others can't access the valueOther changes:
Executor for callbacks per-RPCLoadBalancer now uses generics to no longer depend on any internal classesMetadata.keys() for iterating over all metadataConcurrentModificationException caused when new RPCs are being made when we transition to a freshly-connected transportScheduledExecutorService; you must provide one when setting a deadlineByteBuffer leak when queued RPCs fail (#1401)onReady() correctly (#875)StatusRuntimeException instead of a RuntimeExceptionOkHttpChannelBuilder.overrideHostForAuthority() is deprecated; use overrideAuthority() which is available on all ManagedChannelBuilders
General:
{ManagedChannel,Server}Builder.directExecutor() for low-latency use cases, with specialized handling internally to remove unnecessary locking{Client,Server}Call.request() is now defined as thread-safeAndroid:
SSLCertificateSocketFactoryOkHttpChannelBuilder.overrideHostForAuthority() is deprecated; use overrideAuthority() which is available on all ManagedChannelBuildersjavanano_use_deprecated_packageServers/Datacenter:
ManagedChannelBuilder.loadBalancerFactory. Expect more in this area in the futureManagedChannel.forTarget(). Providing custom name resolvers is supported via ManagedChannelBuilder.nameResolverFactory. Currently only DNS is implemented. Expect more in this area in the futureContext:
Context helpers for Executors: Context.wrap(Executor) and Context.propagate(Executor). The former uses the current context whereas the latter uses the current Context when Executor.execute() is calledContext no longer maintains a stack of attachments and now just maintains the "current". Now, attach() returns the previously-attached Context which is then required to be passed to Context.detach(). This allows naturally restoring a consistent state when applications have bugs when attached/detaching ContextsContext now notifies all its direct listeners before notifying child contextsContext on both client and server. For client, the current Context during new call creation will be the current context during callbacks. For server, a new Context is created for each incoming call and cancelled when server respondsOne column per quarter.