NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central, #738 by repository stars
gRPC: 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
9 years old
167 releases · first in 2018
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…
This release resolves proxy hang issue during initial protocol negotiation, users using proxy should upgrade.
This release resolves proxy hang issue during initial protocol negotiation, users using proxy should upgrade.
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.This release resolves the DoS vulnerability CVE-2019-9515 (SETTINGS flood). Users using the grpc-netty server with untrusted clients should upgrade.
This release resolves the DoS vulnerability CVE-2019-9515 (SETTINGS flood). Users using the grpc-netty server with untrusted clients should upgrade.
@Nullable to getter for trailers on StatusRuntimeException (#5951)onReady if the call is UNARY or SERVER_STREAMING for performance optimization. Users relying on onReady need to migrate. (Note: ADDED on 2/3/20)@aaliddell Adam Liddell @DarrienG Darrien Glasser @jadekler Jean de Klerk @lberki Lukacs T. Berki @liym stbridge @mkobit Mike Kobit @tiggerlee2 Shuangtai Li @zhaonian Zhaonian Luan
This release resolves proxy hang issue during initial protocol negotiation, users using proxy should upgrade.
This release resolves proxy hang issue during initial protocol negotiation, users using proxy should upgrade.
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.This release resolves the DoS vulnerability CVE-2019-9515 (SETTINGS flood). Users using the grpc-netty server with untrusted clients should upgrade.
This release resolves the DoS vulnerability CVE-2019-9515 (SETTINGS flood). Users using the grpc-netty server with untrusted clients should upgrade.
Fix IllegalStateException when transport is terminated (#5955). This is due to a race that seems to mainly impact OkHttp clients. While we believe all
IllegalStateException when transport is terminated (#5955). This is due to a race that seems to mainly impact OkHttp clients. While we believe all transports are affected, it may trigger very rarely. If you see an exception with the message “activeTransport still points to this transport. Seems transportShutdown() was not called.” then you are impacted by the bug.//compiler:grpc_java_plugin is publicly visible again (#5953). The target wasn't publicly visible since v1.21.0. This target was used by rules_proto.api: deprecate Helper.updateSubchannelAddresses() and add equivalent on Subchannel
This release resolves the DoS vulnerability CVE-2019-9515 (SETTINGS flood). Users using the grpc-netty server with untrusted clients should upgrade.
This release resolves the DoS vulnerability CVE-2019-9515 (SETTINGS flood). Users using the grpc-netty server with untrusted clients should upgrade.
LoadBalancer.handleResolvedAddressGroups() is deprecated
io.grpc (not subpackages) were moved to a new artifact “grpc-api”, from grpc-core (#5590). This allows using the API without bringing in as many dependencies, and makes it easier for libraries to have an optional dependency on the rest of grpc. grpc-core now depends on grpc-api. Many users should be able to depend on grpc-api instead of grpc-core if they wish. grpc-core still contains the in-process transport, io.grpc.util, and internal classes used elsewhere in grpc. Most users should still expect to have at least a transitive dependency on grpc-core.MethodDescriptor.MarshallerNameResolverRegistry (#5586). It is now possible to construct a NameResolverProvider and register it into the global map manually. This is useful to inject dependencies into the name resolver.getService() method on MethodDescriptor (#5633)LoadBalancer.handleResolvedAddresses() API for handling resolved addresses which includes service config explicitly (#5499). LoadBalancer.handleResolvedAddressGroups() is deprecatedNameResolver.Args that deprecates NameResolver.Helper. (#5664)LoadBalancer.Helper and Subchannel further non-thread-safe (#5718)LoadBalancer.CreateSubchannelArgs with custom options (#5640)ManagedChannelBuilder.loadBalancerFactory() and all deprecated factories (#5480). Use LoadBalancerRegistry and ManagedChannelBuilder.defaultLoadBalancingPolicy() insteadClientStreamTracer.StreamInfo to a final class with a builder (#5648)ForwardingClientStreamTracer class for delegation use (#5589)StreamObserver.onNext() is called after onCompleted() (#5656)netty-transport-native-epoll and epoll supported OS (linux) (#5581)Thanks to all of our contributors:
core: Deprecated ClientStreamTracer.Factory#newClientStreamTracer is now deleted
Thanks to all of our contributors:
Deprecated previous NameResolver.newNameResolver() overload
grpc-bom is added (#5209)DEFAULT_CONNECTION_SPEC from OkHttpChannelBuilder (#5309)Thanks to all of our contributors:
core: Fixed typo in deprecation warning in RoundRobinLoadBalancerFactory (#5117). The balancer has the name round_robin in the registry (not round-rob…
round_robin in the registry (not round-robin)StreamObservers.copyWithFlowControl() only calls onComplete once (#4558)Thanks to all our external contributors:
Arnout Engelen @raboof Brendan Linn @ubehebe David Hoover @deadmoose Grant Oakley @groakley Rodrigo Queiro @drigz ST-DDT @ST-DDT Thomas Broyer @tbroyer Venil Noronha @venilnoronha Ze'ev Klapow @zklapow
Bazel users should no longer see “java.util.ServiceConfigurationError: io.grpc.LoadBalancerProvider: Provider io.grpc.util.SecretRoundRobinLoadBalance
core: LoadBalancer.Helper.runSerialized() is deprecated in favor of newly introduced getSerializationContext().
Do not use this release. Its handling of gRPCLB causes problems for the ecosystem
maxInboundMetadataSize() to ManagedChannelBuilder and ServerBuilder (#4897). It is now also implemented by the inprocess and okhttp transportsCallCredentials.MetadataApplier from an abstract class back to an interface, as it was in 1.15.x. Introduce a new CallCredentials2.MetadataApplier that is an abstract class, instead. This is ABI incompatible with 1.16.0 but ABI compatible with 1.15.x and 1.16.1 (#5007)final, as there is no purpose in overriding them. (#4954)Thanks to all our external contributors:
Change CallCredentials.MetadataApplier from an abstract class back to an interface, as it was in 1.15.x. Introduce a new CallCredentials2.MetadataAppl
CallCredentials.MetadataApplier from an abstract class back to an interface, as it was in 1.15.x. Introduce a new CallCredentials2.MetadataApplier that is an abstract class, instead. This is ABI incompatible with 1.16.0 but ABI compatible with 1.15.x (#5007)This version had an inadvertent ABI breakage in the @ExperimentalApi CallCredentials. Please use v1.16.1 instead.
This version had an inadvertent ABI breakage in the @ExperimentalApi CallCredentials. Please use v1.16.1 instead.
Thanks to all our external contributors:
OkHttp users are encouraged to upgrade, although if you aren't seeing the particular error mentioned below then you aren't strongly impacted. This is
OkHttp users are encouraged to upgrade, although if you aren't seeing the particular error mentioned below then you aren't strongly impacted. This is normally because you are doing small RPCs.
Non-Android users are encouraged to try enabling gRPC-LB on client-side in their environment and report any problems, even if you aren't interested in gRPC-LB. This will cause additional SRV lookups from DNS. We want to make sure it won't cause issues before enabling it by default.
-Dio.grpc.internal.DnsNameResolverProvider.enable_grpclb=true, which will become the default in the future. We encourage users to try out the option and report back issues, especially additional connecting latency, to https://github.com/grpc/grpc-java/issues/4898.transportExecutor(), sslSocketFactory(), and scheduledExecutorService() are now deprecated in favor of calling the same methods on OkHttpChannelBuilde…
Java 6 is no longer supported. Java 7 is the oldest supported Java version. Android support is unchanged at API level 14. See the announcement. Contrary to the announcement, grpc-context is requiring Java 7. If any Java 7 requirement is causing you issue, please file a GitHub issue.
GoogleCallCredentials can now be sent via ALTS channel (#4657)--use_alts default in the usage printout (#4538)ProxyDetectorImpl (#4677)AndroidChannelBuilder.fromBuilder() (#4723). transportExecutor(), sslSocketFactory(), and scheduledExecutorService() are now deprecated in favor of calling the same methods on OkHttpChannelBuilder before passing it to AndroidChannelBuilder.fromBuilder(). While AndroidChannelBuilder still depends on OkHttpChannelBuilder, it no longer has to duplicate the API.GoogleDefaultChannelBuilder that sets up a secure channel using ALTS if on a properly configured Google Compute Engine instance and using TLS as fallback (#4742). In this release it adds little value unless you enable -Dio.grpc.internal.DnsNameResolverProvider.enable_grpclb=true and have a GCE environment with ALTS enabled. In the future it will become the expected way to create a connection to googleapis.com.StatusException and StatusRuntimeException’s constructors with trailers are now stabilized (#4686).StatusException and StatusRuntimeException’s getTrailers() are now stabilized (#4697)InProcessSocketAddress now forbids null names and has better-defined equality. (#4728)@Deprecated if option deprecated = true is set from the proto file (#4741)Thanks to all our external contributors:
OkHttpChannelBuilder#negotiationType is now deprecated
Notice: This is expected to be the last version supporting Java 6. Comment on #3961 if this causes you trouble. Android API level 14 support will be unchanged.
Updated to Netty 4.1.27 and Netty TCNative 2.0.12
gRPC is now regularly tested with JDK 9 and 10
Warning, a bug was discovered after this release where using Netty Epoll would increase memory usage. Please avoid this release of gRPC if you know you use Netty Epoll
OkHttpChannelBuilder#negotiationType is now deprecatedRpcMethod annotation for use with annotation processorsList<EquivalentAddressGroup> to LoadBalancer Subchannels, in addition to the option of providing a EquivalentAddressGroup (EAG). This prevents the need for LoadBalancers to "flatten" a List<EquivalentAddressGroup> into a single EquivalentAddressGroup which loses/confuses the EAG's Attributes. NameResolvers can now specify Attributes in an EAG and expect that the values are passed to gRPC's core. Future work will add List<EAG> for OobChannels.toString() methodenterIdle() will exit idle mode if channel is still in use (#4665)TransmitStatusRuntimeExceptionInterceptor now avoids accidentally double closing the call.StreamObserver interaction with thread safetyThanks to all our Contributors:
Fix regression that broke Java 9 ALPN support. This fixes the error "SunJSSE selected, but Jetty NPN/ALPN unavailable" (#4620).
CallOptions API: Deprecated CallOptions.Key.of, added CallOptions.Key.create and CallOptions.Key.createWithDefault, and stabilized CallOptions.Key and…
v1.13.0 wasn’t published to maven central due to a releasing process issue and the tag was deleted. The binaries of v1.13.0 were effectively the same as v1.13.1.
FOO_METHODProtoUtils now has metadataMarshaller analogous to ProtoLiteUtilsjsonMarshaller has been removed from grpc-java library (and added into examples)@CheckReturnValue annotation to AbstractStub, CallOptions, and Context
CallOptions API: Deprecated CallOptions.Key.of, added CallOptions.Key.create and CallOptions.Key.createWithDefault, and stabilized CallOptions.Key and CallOptions.withOptionManagedChannelBuilder.maxInboundMessageSize APIGrpcCleanupRule which is more flexible to use than GrpcServerRulePRIVACY_AND_INTEGRITY for GoogleCredentialstoString() to ClientCallImpl and GrpcFuture
Attributes.hashCode() methodCallCredentials.ATTR_SECURITY_LEVEL from transportsClientCall and ClientCall.ListenerServerInterceptor.interceptCall API
Fix regression that broke Java 9 ALPN support. This fixes the error "SunJSSE selected, but Jetty NPN/ALPN unavailable" (#4620).
okhttp: Convert to internal ConnectionSpec eagerly and deprecate OkHttpChannelBuilder.DEFAULT_CONNECTION_SPEC (#4267). After DEFAULT_CONNECTION_SPEC i…
CronetChannelBuilder.scheduledExecutorService() so application can be in control of all threads (#4249)TRANSPORT_ATTR_REMOTE_ADDR (#4217)InputStream overloads for ServerBuilder.useTransportSecurity() and GrpcSslContexts.forServer()AndroidChannelBuilder (#4172). This is an Android-oriented builder and able to receive an Android Context.-Dio.grpc.internal.DnsNameResolverProvider.enable_jndi=true and creating the appropriate DNS TXT record. This will be documented more thoroughly in the near future. There are numerous caveats with this feature and thus is not ready for general usage.awaitTerminated() to return true or call shutdownNow() to avoid the warningOkHttpChannelBuilder.DEFAULT_CONNECTION_SPEC (#4267). After DEFAULT_CONNECTION_SPEC is removed this will save around 40 methods@since for StatusProto.fromStatusAndTrailers (#4287)One column per quarter.