NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central
Maven Central, #741 by repository stars
gRPC: BOM
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
8 years old
155 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
netty: Include pseudo-headers in GrpcHttp2RequestHeaders.iterator() (v1.85.x backport) by @AgraVator in https://github.com/grpc/grpc-java/pull/13120
binder: Add Context-based hasPermissions() to SecurityPolicies and deprecate the PackageManager version.
NettyChannelBuilder.neverIndexMetadataKey() and neverIndexMetadataKeys() so callers can mark selected outbound metadata keys for HPACK's never-indexed literal representation.hasPermissions() to SecurityPolicies and deprecate the PackageManager version.NullPointerException: Http2Error cannot be null for GOAWAY and RPCs could hang until their deadline. Such codes are now treated as INTERNAL_ERROR, so the transport shuts down cleanly.java_grpc_library and java_lite_grpc_library now invoke protoc through Protobuf's proto_lang_toolchain instead of always using @com_google_protobuf//:protoc. They now use the same protoc and protoc options as java_proto_library.ServerCall and ServerCall.Listener. This allows events to be triggered on the ServerCall and be delivered as a listener callback.
@kkalin68
@petedmarsh
Your coding agent can read these notes before it upgrades. Set up the MCP server →
xDS: fix DistributorWatcher thread safety in CertificateProvider- #13087
Nothing published for this version
core: Gracefully handle GOAWAY frames with unrecognized error codes (#13043). Treats unrecognized HTTP/2 GOAWAY error codes as INTERNAL_ERROR instead
…, it missed Netty's built-in CVE-2026-47244 patch. This left a pre-handshake window where the server's local connection allowed up to Integer.MAX_VALU…
In this release we drop support for Android API level 23 or lower (Marshmallow or earlier), following Google Play Service’s now requiring a minimum of API level 24 (Android 7.0 Nougat).
XdsServerBuilder with SocketAddresses (#12925) (ac02c6f)shutdownNow() becoming a no-op after shutdown() (#12982) (3cb7007)DefaultHttp2Connection initialization. Because NettyServerHandler instantiates DefaultHttp2Connection directly rather than using Netty's AbstractHttp2ConnectionHandlerBuilder, it missed Netty's built-in CVE-2026-47244 patch. This left a pre-handshake window where the server's local connection allowed up to Integer.MAX_VALUE active client-initiated streams until a SETTINGS_ACK was received. Enforcing the limit proactively at startup closes this vulnerability window and prevents client-initiated stream floods / resource exhaustion.AsyncServletOutputStreamWriter detect and handle write when not ready (#12732) (46f3080) In highly concurrent scenarios, cached servlet container ready to write state can become stale. The servlet container may have already transitioned to a 'not ready' state, but the corresponding callback has not yet updated gRPC's internal state. This fix makes the ready state to be evaluated explicitly before attempting to write directly to the servlet output stream.@Zhengcy05
@carl-mastrangelo
@themechbro
@JasonLunn
@martinbaillie
@eado
@TimurRakhmatullin86
netty: Fix client-initiated stream limit bypass in NettyServerHandler (#12942). Enforces the limit proactively at startup without waiting for SETTINGS
api: Turn on RFC 3986 parsing by default and update javadoc.
tian__mi__mi@
codingkiddo@
Zhengcy05@
netty: Fix client-initiated stream limit bypass in NettyServerHandler (#12941). Enforces the limit proactively at startup without waiting for SETTINGS
The fixes that were supposed to go in this release were not included in the patch by mistake. Use 1.82.4 instead.
The fixes that were supposed to go in this release were not included in the patch by mistake. Use 1.82.4 instead.
Revert "xds: reuse connections to the control plane across channels" added in 1.81.0 (#12886). If using xds heavily with many targets, then MAX_CONCUR
protoc-gen-grpc-java: Fix missing osx-x86_64 binary (https://github.com/grpc/grpc-java/pull/12878). This fixes a regression in v1.82.0
This release drops support for Bazel 7. It may still run, but we are no longer testing it. We are testing Bazel 8 and 9\.
This release drops support for Bazel 7. It may still run, but we are no longer testing it. We are testing Bazel 8 and 9.
We are anticipating requiring Netty 4.2 in the next release. Please file an issue if you still need Netty 4.1 support.
UNIMPLEMENTED, which tears down the stream and EDS data never arrives. This fix makes it skip DiscoveryRequests for resource types we don't actually subscribe to on a given server.@ThreadSafe annotation and replace with JavaDoc (#12762). Removes JSR-305 annotations but instead of replacing it with ErrorProne's ThreadSafe, sticks to adding a JavaDoc comment. This is done only in public non-final classes and interfaces. This allows Java applications that have moved away from javax to compile and avoids a bug in Immutables and Lombok (and possibly other annotation processors) from failing when JSR-305 is not present.streamClosed() happens before serverCallStarted().GRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST=true when accepting resolved addresses and in CONNECTING state (#12814). It makes sure that whenever PickFirstLeafLoadBalancer transitions into CONNECTING the current address in the addressIndex has a corresponding subchannel. This prevents an NPE in acceptResolvedAddresses in some situations.?force-xds query parameter in the google-c2p resolver (#12760) (86fa86063). This disables environment checks and uses xDS unconditionally. Please note that this feature has not yet seen comprehensive testing.@becomeStar
@bengtsson1-flir
@jnowjack-lucidchart
@Kainsin
@kenkangxgwe
@mfperminov
@paulmurhy123
@schiemon
@therepanic
Revert "xds: reuse connections to the control plane across channels" added in 1.81.0 (#12887). If using xds heavily with many targets, then MAX_CONCUR
api: Deprecate LoadBalancer.handleResolvedAddresses(). Developers maintaining custom LoadBalancer implementations should transition to using LoadBalan…
In this release we drop support for Android API level 22 or lower (Lollipop or earlier), following Google Play Service’s discontinued updates for Lollipop (API levels 21 & 22) and now requires a minimum of API level 23 (Android 6.0 Marshmallow).
API Changes
Behavior Changes
android.context.Context. For reference, it seems Chrome caches for 1 minuteBug Fixes
ManagedChannelOrphanWrapper could incorrectly log a "not shutdown properly" warning during garbage collection when using directExecutor(). (#12705) (d459338)typeUrl. (#12740) (eac9fe9)backend_service. This ensures xDS load balancing metrics are reported accurately. (#12735)New Features
grpc.client.call.custom label as defined by gRFC A108. See also the gRPC OpenTelemetry Metrics guide (update in-progress)AdvancedTlsX509KeyManager so that developers can now preserve and use key aliases when dynamically reloading TLS certificates. (#12686)Documentation
Dependencies
Thanks to
core: Added PickResult.copyWithSubchannel() and PickResult.copyWithStreamTracerFactory() to simplify updating PickResult while preserving metadata. Lo
API Changes
Bug Fixes
Improvements
New Features
Thanks to
core: Delete the never-used io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (#12580) (738782fb0). This is deeply internal and not accessible, so
API Changes
core: Delete the never-used io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (#12580) (738782fb0). This is deeply internal and not accessible, so shouldn’t impact anything. However, Apache Arrow Java uses reflection to access private fields; GH-939: Remove reflection for gRPC buffers is swapping to gRPC’s public zero-copy APIs
opentelemetry: Add target attribute filter for metrics (#12587). Introduce an optional Predicate targetAttributeFilter to control how grpc.target is recorded in OpenTelemetry client metrics. When a filter is provided, targets rejected by the predicate are normalized to "other" to reduce grpc.target metric cardinality, while accepted targets are recorded as-is. If no filter is set, existing behavior is preserved. This change adds a new Builder API on GrpcOpenTelemetry to allow applications to configure the filter.
Behavior Changes
core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an internal refactoring, but it does improve how errors are handled for broken binaries. Previously, not being able to load pick_first would result in a channel panic. Now it is handled as a regular load balancing error
okhttp: Assert no pending streams before transport READY (#12566) (ed6d175fc). No pending streams should exist when the transport transitions to READY. This PR adds an assertion to help verify this invariant.
Bug Fixes
core: PickFirstLB should not return a subchannel during CONNECTING (228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, and it was of no consequence. However, now there are some load balancing policies (mainly RLS) that will do a pick() and hope the result to be reasonably accurate for metrics.
xds: Endpoint weights are now normalized within localities, so that when using rish_hash the locality weights are preserved (f6d140f87). Previously, localities with many endpoints or high endpoint weights could receive excess traffic. This is one part of gRFC A113 pick_first: Weighted Random Shuffle
Improvements
core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). Previously the error message contained “buffered_nanos” and “waiting_for_connection” for connection delays. However, we discovered the same strings were also used if waiting on CallCredentials. Now you’ll see details like “connecting_and_lb_delay”, “call_credentials_delay”, and “was_still_waiting”.
opentelemetry: Add Android API checking (a9f73f4c0). Previously we assumed OpenTelemetry support would not be used on Android. It did happen to be compatible with Android, but since OpenTelemetry does have some Android support, we now have a check that it remains compatible
core: Catch Errors when calling complex config parsing code (a535ed799). Error (and any other Throwable) is now caught and handled when parsing configuration (e.g., service config, xds). This will cause such failures to be handled gracefully instead of panicking the channel
core: Implement LoadBalancer.Helper.createOobChannel() with the internals of createResolvingOobChannel() (3915d029c). This API is only expected to be relevant to the gRPC-LB lookaside load balancer, and is not believed to have behavior changes. Out-of-band channel had been implemented with its own stripped-down Channel without load balancing. Reimplementing using the resolving oob channel makes it a full-fledged channel and reduces the burden when integrating new features and allows us to have a ManagedChannelBuilder to use with efforts like gRFC A110: Child Channel Options.
xds: Implement the proactive connection logic in RingHashLoadBalancer as outlined in gRFC A61 (#12596). Previously, the Java implementation only initialized child balancers when a ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel call. This PR adds the missing logic: when a child balancer reports TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first available IDLE child if no other children are currently connecting or ready.
This ensures a backup subchannel starts warming up immediately outside the RPC flow, reducing failover latency and improving overall resilience. This behavior was previously present but was inadvertently lost after #10610.
New Features
Dependencies
protobuf: Upgrade Bazel protobuf to 33.1 (#12553) (b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)
protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and grpc-proto versions (#12569)
Upgrade dependencies (#12588) (6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 1.41.0, proto-google-common-protos to 2.63.2.
Thanks to
core: Fix shutdown failing accepted RPCs during channel startup (02e98a806). This fixes a race where RPCs could fail with "UNAVAILABLE: Channel shutdo
this from BinderServerTransport's ctor (#12453) (89d77e062)android:isolatedProcess Services and moves all security checks to the handshake, making subsequent transactions more efficient.random_subsetting_experimental. If it is working for you, tell us so we can gauge marking it stable. While the xDS portions haven’t yet landed, it is possible to use with xDS with JSON-style Structs as supported by gRFC A52CertificateValidationContext message (see envoyproxy/envoy#34235) has a system_root_certs field. In the gRPC client, if this field is present and the ca_certificate_provider_instance field is unset, system root certificates will be used for validation. This implements gRFC A82.trusted_xds_server in the server_features field.rls: Avoid missed config update from reentrancy (https://github.com/grpc/grpc-java/pull/12549). This fixes a regression since 1.75.0 triggered by CdsL
binder: Remove experimental BinderChannelBuilder.bindAsUser() method, deprecated since 1.69 (\#12401)
BinderChannelBuilder.bindAsUser() method, deprecated since 1.69 (#12401) (f96ce0670)GOAWAY: too_many_pingsFileWatcherCertificateProvider isn't used when using system root trust store, the SslContext update for the handshake that depended on it wasn't happening. This fix creates a separate CertificateProvider for handling system root certs that doesn't rely on the FileWatcherCertificateProvider.GcpAuthenticationFilter in the filter chain to make available the cluster resource in CallOptions.trusted_xds_server in the bootstrap. System root cert support and SNI require using XdsChannelCredentials@panchenko @benjaminp @HyunSangHan @becomeStar @ZachChuba @oliviamariacodes @kssumin @laz-canva
Downgrade OpenTelemetry to 1.51.0 to make it easier for people dealing with the OkHttp 4.x → 5.x upgrade of some OpenTelemetry modules (354d8b451). gR
rls: Avoid missed config update from reentrancy (https://github.com/grpc/grpc-java/pull/12550). This fixes a regression since 1.75.0 triggered by CdsL
core: Fix NullPointerException during address update with Happy Eyeballs (5e8af564e). This should not impact many people as the code is disabled by de
xds: ClusterResolverLb has been converted to use XdsDepManager, which finishes the changes for gRFC A74 xDS Config Tears. This change should resolve s
@JoeCqupt @Sangamesh1997 @benjaminp @camelcc @dmytroreutov @duckladydinh @jirkafm @kilink @panchenko @umairk79 @vimanikag @werkt @xuhongxu96 @zrlw
…without upgrading which causes problems for vulnerability tracking.
grpc-timeout should always be positive (#12201) (6dfa03c51). There is a local race between when the deadline is checked before sending the RPC and when the timeout is calculated to put on-the-wire. The code replaced negative timeouts with 0 nanoseconds. gRPC’s PROTOCOL-HTTP2 spec states that timeouts should be positive, so now non-positive values are replaced with 1 nanosecondNettyServerBuilder.maxRstFramesPerWindow() limit (#12288). This extends the Rapid Reset tool to also cover MadeYouReset. the reset stream count will cause a 420 "Enhance your calm response" to be sent. This depends on Netty 4.1.124 for a bug fix to actually call the encoder by the frame writer.XdsDepManager (297ab05ef). This is part of gRFC A74 to have atomic xDS config updates. This is an internal change, but does change the error description seen in certain cases, especially DEADLINE_EXCEEDED on a brand-new channel.BlockingClientCall infinite blocking (#12217) (ba0a7329d). Move deadline computation into overloads with finite timeouts. Blocking calls without timeouts now do not have to read the clock.Metadata values to be exchanged during a call (#12229) (80217275d)failOverTimer which would then wait the 10 seconds for the child to finish CONNECTING. We only want to give the child one opportunity after transitioning out of READY/IDLE.XdsClientImpl and ControlPlaneClient (#12287). ControlPlaneClient uses "xds-cp-client" now instead of "xds-client" while logging.NettyAdaptiveCumulator (#11284), which can have a performance impact. We delayed upgrading Netty to give time to rework the optimization, but we've gone too long already without upgrading which causes problems for vulnerability tracking.jar_jar to avoid xds deps (#12243) (8f09b9689). The //xds and //xds:orca targets now use jar_jar to shade the protobuf generated code. This allows them to use their own private copy of the protos and drop direct Bazel dependencies on cel-spec, grpc, rules_go, com_github_cncf_xds, envoy_api, com_envoyproxy_protoc_gen_validate, and opencensus_proto. This mirrors the shading of protobuf messages done for grpc-xds provided on Maven Central and should simplify dependency management@SystemApi runtime visibility requirement isn't really new. It has always been implicit in the required INTERACT_ACROSS_USERS permission, which can only be held by system apps in production. Now deprecated BinderChannelBuilder#bindAsUser has always required SDK_INT >= 30. This change just copies that requirement forward to its replacement APIs in AndroidComponentAddress and the TARGET_ANDROID_USER NameResolver.Args.NameResolver.Listener2 interface (#12220) (d352540a0)@benjaminp @werkt @kilink @vimanikag
compiler: Default to @generated=omit (f8700a13a). This omits javax.annotation.Generated from the generated code and makes the org.apache.tomcat:annota
@generated=omit (f8700a13a). This omits javax.annotation.Generated from the generated code and makes the org.apache.tomcat:annotations-api compile-only dependency unnecessary (README and examples changes forthcoming; we delayed those changes until the release landed). You can use the option @generated=javax for the previous behavior, but please also file an issue so we can develop alternativesStatusRuntimeException. However, feedback demonstrated it was confusing to mix that with the checked StatusException in BlockingClientCall. Now the new blocking stub uses StatusException throughout. grpc-java continues to support the old generated code, but the version of protoc-gen-grpc-java will dictate which API you see. If you support multiple generated code versions, you can use the older blocking v1 stub for unary RPCsNullPointerException in ClusterImplLoadBalancer.createSubchannel(), which had a ring_hash child. This is most likely to help xDS, as it heavily uses hierarchical LB policies--incompatible_disable_target_default_provider_fieldsxds: Enable least request by default (#12062) core: Delete the long-deprecated GRPC_PROXY_EXP env variable (#11988) (908f9f19c). This was experimental…
xds: Enable least request by default (#12062) core: Delete the long-deprecated GRPC_PROXY_EXP env variable (#11988) (908f9f19c). This was experimental and has been warning when used since v1.8.0. Use the Java-standard -Dhttps.proxyHost and -Dhttps.proxyPort instead api: Remove deprecated SubchannelPicker.requestConnection() (f79ab2f16). This API was replaced by LoadBalancer.requestConnection() in v1.22.0
config: prevents global stats config freeze in ConfiguratorRegistry.getConfigurators() (#11991) (d4c46a7f1) xds: XdsDepManager should ignore updates after shutdown (25199e9df). This fixes a source of java.lang.NullPointerException: Cannot invoke "io.grpc.xds.XdsDependencyManager$RdsUpdateSupplier.getRdsUpdate()" because "routeSource" is null regression introduced in v1.72.0
xds: listener type validation (#11933) (c8d1e6e39) xds: add the missing xds.authority metric defined in gRFC A78 (#12018) (6cd007d0d)
xds: float LRU cache across interceptors (#11992) (7a08fdb7f) xds: propagate audience from cluster resource in gcp auth filter. This completes the gRFC A83, implementation of GCP Authentication Filter. (#11972) (84c7713b2) opentelemetry: Implement grpc.lb.backend_service optional label (961945379). This completes the gRFC A89 implementation, which is enabled when requesting the new label
api: Remove mention of "epoch" from Ticker.nanoTime() javadocs (84bd01454)
util: Remove deprecated method GracefulSwitchLb.switchTo() (f207be39a). It is rarely used outside of gRPC itself. The configuration is passed as lb po…
@panchenko @emmanuel-ferdman @JoeCqupt
xds: Enable Xds Client Fallback by default. This allows having a backup xDS server as described in gRFC A71-xds-fallback.md
ProtoUtils is now stabilized (#11884) (90b1c4fe9)CheckReturnValue with Error Prone's (#11811) (7b5d0692c)MessageFramer.flush() is being called between every message, so messages are never combined and the larger allocation just wastes memory. (4a10a3816, 7153ff852)ClientStreamObserver closes the response observer log the error message if this operation fails (#11880) (302342cfc)AltsContextUtil to allow getting the AltsContext on client-side (b1bc0a9d2)HelloWorldServer to use Executor (#11850) (16edf7ac4)@benjamin @panchenko @harshagoo94 @NaveenPrasannaV
okhttp: Improve certificate handling by rejecting non-ASCII subject alternative names and hostnames as seen in CVE-2021-0341 (\#11749) (a0982ca0a). Ho…
grpc.target label in grpc.xds_client.* metrics. Previously the empty string was usedokhttp: Improve certificate handling by rejecting non-ASCII subject alternative names and hostnames as seen in CVE-2021-0341 (\#11749) (a0982ca0a). Ho…
services: Deprecate ProtoReflectionService (\#11681) (921f88ae3). The class implements the deprecated v1alpha of the reflection protocol. Prefer Proto…
v1.69.0
New Features
LoadBalancers to specify an authority per-RPC.(#11631) (c167ead85) CallOptions.withAuthority() has higher precedence.GoogleDefaultChannelCredentials (#11634) (ba8ab796e)grpc.xds.authority is not yet availableBug Fixes
Listener onAddresses to Listener2 continue to use onResult (#11666) (dae078c0a). This fixes a 1.68.1 "IllegalStateException: Not called from the SynchronizationContext" regression (#11662) that could be seen in certain custom NameResolversImprovements
java.time.Duration overloads to CallOptions, AbstractStub methods that take TimeUnit and a time value (#11562) (766b92379)AndroidComponentAddress specify a target UserHandle (#11670) (e58c998a4)Dependencies
Documentation
Thanks to
@niloc132
@rockspore
@SreeramdasLavanya
@vinodhabib
okhttp: Improve certificate handling by rejecting non-ASCII subject alternative names and hostnames as seen in CVE-2021-0341 (\#11749) (a0982ca0a). Ho…
api: When forwarding from Listener onAddresses to Listener2 continue to use onResult (https://github.com/grpc/grpc-java/pull/11688). This fixes a 1.68
Updated protobuf-java to 3.25.5. This helps avoid CVE-2024-7254
v1.68.0 was a mistake. This is the first release of version 1.68.x
builder.transportExecutor() runs out of threads (e.g., it is a fixed-size thread pool), all transports can be wedged, unable to run on-demand tasks, until keepalive kills one of them. Two threads are now used when handshaking a new transport, and the transport will time out after 1 second with “Timed out waiting for second handshake thread” if two threads are unavailablemesh_id value from CSM_MESH_ID environment variable, instead of getting it from bootstrap file (84d30afad)io.grpc.Context storage override to store its state in io.opentelemetry.context.Context. Libraries should not add a dependency on this artifact, as applications can only have one storage override in their classpathio.grpc.s2a.S2AChannelCredentialsStreamTracer.inboundMessageRead() now reports uncompressed message size when the message does not need compression (#11598) (2aae68e11). Previously it always reported -1 (unknown)UdsChannelBuilder, use fake IP instead of localhost (a908b5e40). This avoids an unnecessary DNS lookupGRPC_EXPERIMENTAL_ENABLE_OTEL_TRACING environment variable to true to enable tracing support in GrpcOpenTelemetry (#11409, #11477)(043ba55, 421e237)Thanks to:
@Juneezee
@lgalfaso
@bestbeforetoday
@hlx502
@JoeCqupt
This was supposed to be v1.67.0, but there was a mistake during the release process. This has everything in v1.67.1, _except_ for:
This was supposed to be v1.67.0, but there was a mistake during the release process. This has everything in v1.67.1, except for:
There was no 1.67.0 release. There was a problem making the release and it went to Maven Central as 1.68.0 instead. This is a version-corrected releas
There was no 1.67.0 release. There was a problem making the release and it went to Maven Central as 1.68.0 instead. This is a version-corrected release.
@Juneezee @lujiajing1126 @JarvisCraft @sunpe
util: Add GracefulSwitchLoadBalancer config (ebed04798) and mark switchTo() deprecated. (85e0a01ec). GracefulSwitchLoadBalancer now receives its confi…
AdvancedTlsX509TrustManager, an X509ExtendedTrustManager that allows users to configure advanced TLS features, such as root certificate reloading and peer cert custom verification. (658cbf6cf)GracefulSwitchLoadBalancer config (ebed04798) and mark switchTo() deprecated. (85e0a01ec). GracefulSwitchLoadBalancer now receives its configuration like a regular load balancer.AllowSecurityPolicy to allow calling code to not have to wait on async/slow implementations. BinderTransport now submits async implementations to an executor. (#11272) (7fee6a3fe)ServerBuilder for adding a list of service implementations to the handler registry together. (#11285) (85ed05300)PickFirstLeafLoadBalancer
NettyAdaptiveCumulator if Netty is on version 4.1.111 or later. (#11367)BinderServer own ServerAuthInterceptor's executor that helps avoid leaks. (#11293) (15ad9f546)ProtoReflectionServiceV1 for the v1 reflection protocol. The preexisting ProtoReflectionService implements the v1alpha reflection protocol. (#11237) (0aa976c4e)AdvancedTlsX509TrustManager validation on servers when using SSLSocket. Previously it would try to use a null SSLEngine . (dcb1c018c)@com_github_cncf_udpa usage with preexisting @com_github_cncf_xds; delete @com_github_cncf_udpa repo alias for xds (6dd6ca9f9)artifact() syntax@hlx502 @erm-g @jdcormie @JoaoVitorStein @cfredri4
netty: Restore old behavior of NettyAdaptiveCumulator, but avoid using that class if Netty is on version 4.1.111 or later
grpc-netty in this release is compatible with Netty 4.1.111; it fixes the incompatibility that caused data corruption. grpc-netty-shaded is still usin
grpc-netty in this release is compatible with Netty 4.1.111; it fixes the incompatibility that caused data corruption. grpc-netty-shaded is still using Netty 4.1.100.
ClientStreamTracer.inboundHeaders(Metadata) (960012d76). This is the same as the existing inboundHeaders(), but is provided the Metadata@ExperimentalApi being removed, but it was re-added in 3c97245 before the release@hakusai22 @firov @mateusazis @Mir3605 @niloc132
netty: Restore old behavior of NettyAdaptiveCumulator, but avoid using that class if Netty is on version 4.1.111 or later
netty:Fix Netty composite buffer merging to be compatible with Netty 4.1.111 (1.64.x backport) by @larry-safran in https://github.com/grpc/grpc-java/p
cronet: @javadoc update android permission MODIFY_NETWORK_ACCOUNTING (deprecated) => UPDATE_DEVICE_STATS
Avoid upgrading your application to Netty 4.1.111, with this version as there is a possible corruption. For Netty 4.1.111 compatibility, it is best to use 1.63.2, 1.64.2, 1.65.1, and later. See https://github.com/grpc/grpc-java/issues/11284 .
jakarta_omit was renamed @generated=omit (#11086) (8a21afcc9)@maven targets (00649913b)load() statements for the Bazel builtin top-level java symbols (#11105) (add8c37a4)StatusProto.toStatusException overload to accept Throwable (#11083) (5c9b49231)channel.getState() was delayed until the name resolver returned results. This had no impact to RPC behavior@panchenko @Ashok-Varma @benjaminp @AutomatedTester @hypnoce @keith @laglangyue @rostik404 @ryanpbrewster @abtom @hvadehra @rtadepalli
okhttp: Workaround SSLSocket not noticing socket is closed
netty: Release SendGrpcFrameCommand when stream is missing
api: Stabilize server.getListenerSockets
xds, dual stack, happy eyeballs: Support dual stack in xds, change list includes:
jakarta_omit to protoc-gen-grpc-java when generating codegrpc-xds jar size has decreased by 35%.Alex Panchenko Benjamin Peterson David Ankin Prashanth Swaminathan Touko Vainio-Kaila
services: Remove io.grpc.services.BinaryLogs, which was deprecated since 2021. io.grpc.protobuf.services.BinaryLogs should be used instead (#10832).
Note that this is the initial 1.62.x release
io.grpc.services.BinaryLogs, which was deprecated since 2021. io.grpc.protobuf.services.BinaryLogs should be used instead (#10832).xds: Fix a bug in WeightedRoundRobinLoadBalancer policy that could raise NullPointerException and further cause channel panic when picking a subchanne
xds: Fix a bug in WeightedRoundRobinLoadBalancer policy that could raise NullPointerException and further cause channel panic when picking a subchannel. This bug can only be triggered when connection can not be established and the channel reports TRANSIENT_FAILURE state. (#10868)
api: Deprecate LoadBalancer.EMPTY_PICKER added in 1.58.0 in favor of FixedResultPicker
round_robin pickers (dca89b25b). This makes its implementation more similar to weighted_round_robin.io.grpc.internal) will be less frequently included transitively at compile time.xds: Fix a bug in WeightedRoundRobinLoadBalancer policy that could raise NullPointerException and further cause channel panic when picking a subchanne
xds: Fix a bug in WeightedRoundRobinLoadBalancer policy that could raise NullPointerException and further cause channel panic when picking a subchannel. This bug can only be triggered when connection can not be established and the channel reports TRANSIENT_FAILURE state. (#10868)
util: Fix NPE when multiple addresses in an address group for petiole load balancer policies
Note that ForwardingChannelBuilder is stabilized (no changes will be made to it), but immediately deprecated in favor of ForwardingChannelBuilder2.
ForwardingServerBuilder, ForwardingChannelBuilder2, and ForwardingChannelBuilder. Note that ForwardingChannelBuilder is stabilized (no changes will be made to it), but immediately deprecated in favor of ForwardingChannelBuilder2. (#10586)ForwardingChannelBuilder.delegate(). De facto this deprecates the class itself, since all classes extending ForwardingChannelBuilder implement the delegate() method. See javadoc for details (#10587)LoadBalancer.acceptResolvedAddresses() to return Status instead of boolean (#10636). This is part of continued work to align the LB API cross-language and API stabilizationForwardingChannelBuilder2 (#10587)ProtoUtils.metadataMarshaller() (#10628)ManagedChannels now check the address types provided by the nameResolver (for the given target) with the address types supported by the channel transport and generate an error in case of mismatch. That dramatically improves the error message when an issue occursStatus.UNKNOWN returned to the client will have Application error processing RPC description. Previously the description was empty. This is helpful to differentiate between server errors originated in user application, gRPC library, or even those injected by a proxy. (#10643)Http2Headers.isEmpty(). This fixes compatibility with Netty 4.1.101.Final.NettyServerBuilder.maxRstFramesPerWindow(). This can be used to limit impact of Rapid Reset@anthonyjpratti @fedorka @jpd236 @mateusazis @pkoenig10 @yannickepstein @amirhadadi
netty: Implement Http2Headers.isEmpty(). This fixes compatibility with Netty 4.1.101.Final.
Http2Headers.isEmpty(). This fixes compatibility with Netty 4.1.101.Final.NettyServerBuilder.maxRstFramesPerWindow(). This can be used to limit impact of Rapid Resetapi: Add ForwardingChannelBuilder2, an ABI-safe version of ForwardingChannelBuilder, which will be deprecated in the following release. (#10585, #1040…
PLANNED ABI BREAKAGE!
This breaks the ABI of the @ExperimentalApi classes listed below.
This does not impact source code (API); it only impacts code compiled with a different version of gRPC than it runs with (ABI).
Users that recompiled their code using grpc-java v1.36.0 (released on Feb 23, 2021) and later, ARE NOT AFFECTED.
Users that compiled their source using grpc-java earlier than v1.36.0 may need to recompile when upgrading to grpc-java v1.59.0.
See details in #10406.
Affected classes
Class io.grpc.internal.AbstractManagedChannelImplBuilder is deleted, and no longer in the class hierarchy of the channel builders:
io.grpc.netty.NettyChannelBuilderio.grpc.okhttp.OkhttpChannelBuilderio.grpc.cronet.CronetChannelBuilderClass io.grpc.internal.AbstractServerImplBuilder is deleted, and no longer in the class hierarchy of the server builders:
io.grpc.netty.NettyServerBuilderio.grpc.inprocess.InProcessServerBuilderAbstractManagedChannelImplBuilder and AbstractServerImplBuilder are removed (#10530). This is ABI-breaking, see the warning above. (#10406)v1.36.0 to ease removal of internal ABIs. (#10406)ForwardingChannelBuilder2, an ABI-safe version of ForwardingChannelBuilder, which will be deprecated in the following release. (#10585, #10406)LoadBalancer.FixedResultPicker convenience class for load balancer implementations. It is a replacement for ErrorPicker and EMPTY_PICKER added in 1.58.0John Cormie (@jdcormie) Stephane Landelle (@slandelle) @kotlaja
xds: PickFirst was not receiving its configuration so it used the default configuration which meant that randomize was ignored.
stub: Removed deprecated methods attachHeaders and captureMetadata from MetadataUtils
ServerCall#setMessageCompression() and PartialForwardingServerCall#setMessageCompression() (#10393)ProtoUtils.setExtensionRegistry() and ProtoLiteUtils.setExtensionRegistry() (#10392)GrpcCleanupRule, GrpcServerRule (#10494)GRPC_EXPERIMENTAL_PICKFIRST_LB_CONFIG env variable is true by default now) for xds leaf LB policy (#10475)next() or hasNext() had been called to send the request.Grpc.newServerBuilderForPort(). At present, Netty always has higher priority than OkHttp, if they are both available, because ServerBuilder.forPort() is not supported in the OkHttp transport but is supported in the Netty transportNoSuchMethodError for ByteBuffer methods present in 1.57.0 (#10441) androidx.core:core 1.10.0 -> 1.10.1
com.google.api.grpc:proto-google-common-protos 2.17.0 -> 2.22.0
com.google.cloud:google-cloud-logging 3.14.5 -> 3.15.5
com.google.errorprone:error_prone_annotations 2.18.0 -> 2.20.0
com.squareup.okio:okio 1.17.5 -> 2.10.0
Halvard Skogsrud
util: Outlier detection tracer delegation
Fix compatibility with Java 8. This fixes the NoSuchMethodError for ByteBuffer methods present in 1.57.0
NoSuchMethodError for ByteBuffer methods present in 1.57.0 (#10441)Update guava dependency to 32.0.1 to address CVE-2023-2976
This release accidentally broke Java 8: NoSuchMethodError for some ByteBuffer methods. The issue is tracked in https://github.com/grpc/grpc-java/issues/10432 and fixed in 1.57.1.
UserHandle and BinderChannelCredentials to support cross-user communication (#10197)core: Fix regression in 1.54.0 where polling NameResolvers would not refresh after a resolution error (#10328). The symptom is a transient failure lik
grpc-grpclb is in the classpath. So even users that think "I don't use grpclb" may have been impacted. round_robin is mainly impacted on startup, but if the error happened afterward it would commonly fix itself for short transient DNS failures. pick_first is impacted at all times; any failed DNS resolution could cause all future RPCs on the channel to fail.One column per quarter.