NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central
Maven Central, #744 by repository stars
grpc Examples
Latest stable
0.15.0
Last release 10 years ago
no release in 18 months
Release timing varies
gaps range from 9 days to 4 months
Nearly every release is documented
notes for 13 of 13 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
13 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
generated AbstractService class and interfaces are now deprecated in favor of ServiceImplBase
Your coding agent can read these notes before it upgrades. Set up the MCP server →
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 responds_Hostname verification on Android_, when not providing your own SSLCertificateSocketFactory
SSLCertificateSocketFactoryUpdated to protobuf 3.0.0-beta-1. Codegen supports javanano_use_deprecated_package, but is not using it for determining which package to generate gRPC…
This release of gRPC-Java is considered beta quality.
As of this release, we expect no breaking API changes unless marked otherwise. This applies to API in packages io.grpc, io.grpc.auth, io.grpc.stub, and io.grpc.protobuf, as well as normal protobuf generated code. This does not apply to undocumented behavior; we are very likely to align gRPC-Java with the other gRPC implementations by trying harder before failing RPCs.
The codegen is not yet guaranteed forward-compatible as it uses unstable APIs. This will be resolved by 1.0. For now, you must still use the same version of the gRPC-Java protoc plugin as runtime version.
@Internal should not be used and those marked with @ExperimentalApi may change in the futureStreamObserver.onValue has been renamed to onNext to align with RxJavaChannelImpl should now become ManagedChannelManagedChannelBuilder.forAddress(String, int) is now the preferred way of obtaining a channel builder; all transport-specific APIs do not have guaranteed API stability. Similarly, there is ServerBuilder.forPort(int) for server-sidemaxMessageSize(int) configurationjavanano_use_deprecated_package, but is not using it for determining which package to generate gRPC code. That will change in the next releaseServiceAccountJwtAccessCredentials. In the future will likely support auto-conversion from ServiceAccountCredentials for use with GoogleCredentials.getApplicationDefault()ServerCall.onComplete() is called instead of ServerCall.onCancel(). This was already the behavior, but the documentation now agreesAs we rapidly approach our beta release, we are cleaning up our API and organizing our code to increase maintainability. All breaking changes should h…
As we rapidly approach our beta release, we are cleaning up our API and organizing our code to increase maintainability. All breaking changes should have clear and available alternatives (method and class renames).
This is a patch release of v0.7.x that addresses two issues:
This is a patch release of v0.7.x that addresses two issues:
This is a patch release of v0.7.0 that fixes #504 (via cdd81d2e75ecee6e49dfeaeffcfb4882a8fdbd36). The patch addresses a race condition where multiple
This is a patch release of v0.7.0 that fixes #504 (via cdd81d2e75ecee6e49dfeaeffcfb4882a8fdbd36). The patch addresses a race condition where multiple Netty transports can be created by the same builder, resulting in an unsharable handler being added to multiple Netty pipelines. In addition, better error handling has been added to the bootstrap of TLS pipelines in order to detect errors that occur early on in protocol negotiation that may have previously been missed.
First tagged release of gRPC-Java with artifacts and dependencies on Maven Central, complete with binary protoc plugin.
First tagged release of gRPC-Java with artifacts and dependencies on Maven Central, complete with binary protoc plugin.
gRPC-Java is considered alpha quality and does not yet guarantee API-stability.
One column per quarter.