Update grpc-java monorepo to v1.84.0 - #112
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
February 3, 2024 00:37
8d47c52 to
cb9dac3
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
February 27, 2024 02:34
cb9dac3 to
d60132f
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
April 6, 2024 12:00
d60132f to
524ac09
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
May 23, 2024 02:21
524ac09 to
c04564f
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
June 28, 2024 08:41
c04564f to
4528447
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
July 12, 2024 02:54
4528447 to
fd08624
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
August 11, 2024 00:01
fd08624 to
8614c85
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
September 21, 2024 11:34
8614c85 to
6aa92cb
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
September 28, 2024 06:43
6aa92cb to
9f42dae
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
October 29, 2024 06:11
9f42dae to
74d34b2
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
November 28, 2024 10:13
74d34b2 to
9c8de32
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
December 10, 2024 20:11
9c8de32 to
ae08714
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
January 17, 2025 04:15
ae08714 to
6ac43f2
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
January 22, 2025 13:14
6ac43f2 to
9707da2
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
March 4, 2025 22:54
9707da2 to
6fa79f0
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
July 28, 2025 17:35
881feeb to
a029a4e
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
August 21, 2025 17:00
a029a4e to
76e8f3b
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
October 7, 2025 15:54
76e8f3b to
224fc94
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
November 19, 2025 23:26
224fc94 to
5645d32
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
December 23, 2025 21:49
5645d32 to
3fbdb89
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
February 3, 2026 13:55
3fbdb89 to
58ee436
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
March 17, 2026 17:40
58ee436 to
199b79c
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
April 30, 2026 23:39
199b79c to
f382b10
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
June 10, 2026 17:55
f382b10 to
e6320d9
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
June 23, 2026 21:48
e6320d9 to
fabc452
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
July 9, 2026 21:56
fabc452 to
986836d
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
July 22, 2026 17:16
986836d to
9d8fc67
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
July 30, 2026 08:50
9d8fc67 to
e59135a
Compare
renovate
Bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
September 6, 2026 19:52
e59135a to
ef52167
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.47.0→1.84.01.47.0→1.84.01.47.0→1.84.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
grpc/grpc-java (io.grpc:grpc-stub)
v1.84.0In 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).
API Changes
ac02c6f)XdsServerBuilderwithSocketAddresses (#12925) (ac02c6f)6966536)Behavior Changes
96807d8)Ignore all but the first certificate if the x5c JWK parameter contains multiple values.
Skip the JWK entry instead of stopping execution or throwing when x5c is missing or contains an empty list, complying with the requirement that entries without x5c must be ignored.
Bug Fixes
72c6e5f)Fixes a bug whereby an OOB channel shutdown incorrectly shut down the shared transport factory with the main channel, and the main channel was unable to create subchannels anymore and faced an exception in doing so.
shutdownNow()becoming a no-op aftershutdown()(#12982) (3cb7007)d49a589)296c007) Chains multiple childChannelConfigurator() calls instead of overwriting them in ManagedChannelImplBuilder and XdsServerBuilder, ensuring all configurators are preserved and executed when child channels are created.7843bd4) Caches header_data received in RouteLookupResponse and sends it back as stale_header_data in RouteLookupRequest when refreshing stale cache entries, complying with the RLS specification.Improvements
56205f9) Configure max active streams limit directly uponDefaultHttp2Connectioninitialization. BecauseNettyServerHandlerinstantiatesDefaultHttp2Connectiondirectly rather than using Netty'sAbstractHttp2ConnectionHandlerBuilder, 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.AsyncServletOutputStreamWriterdetect 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.0f859c3) By RFC 9113, section 6.9, receivers must take frames into account for flow control even if they're errored. This change moves the stream error response logic after connection window updates0585d48)bc01994)9fdef96)9ffa1e1)Dependencies
6ccd065). Update the maximum supported edition in the Java gRPC compiler plugin to EDITION_2026 when compiling against Protobuf version 7.35.0 (v35.0) or later.5d0a012)1bc2f5a)Documentation
ee08f53)New Features
073fd5e) Implements attempt-level RPC delay observability across the core delayed transport, built-in load balancers (pick_first, round_robin), RLS, and xDS policies, aligned with gRFC A121. Adds LoadBalancer.PickResult.withNoResult(delayType, delayReason) and delay tracing callbacks on ClientStreamTracer. Records attempt delay duration metrics (grpc.client.attempt.delay.duration) and child tracing spans ("Attempt Delay") via the OpenTelemetry plugin.Thanks to
@Zhengcy05
@carl-mastrangelo
@themechbro
@JasonLunn
@martinbaillie
@eado
@TimurRakhmatullin86
v1.83.1gRPC Java 1.83.1 Release Notes
Improvements
v1.83.0gRPC Java 1.83.0 Release Notes
API Changes
4456721)2b86f8f). This allows users to explicitly provide a NameResolverRegistry during channel creation rather than relying on the global registry, offering better isolation and control over name resolution per-channel.Behavior Changes
3018ce3). v1.82.0 enabled TLS 1.3 for clients; this does the same for servers1e85674) Enables xDS configuration to control which fields get propagated from ORCA backend metric reports to LRS load reports as per gRFC A85c8079ee). This only has an effect when using aggregate clusters3db3235). Previously, modifications to LoadBalancerRegistry could cause failures in the LB treed49c0b1). If using xds heavily with many targets, then MAX_CONCURRENT_STREAMS to the control plane could be exceeded. This then prevents loading resources for new targets, which causes those channels to hang on name resolution. RPCs would see the nondescript "DEADLINE_EXCEEDED: Deadline Context was exceeded after Xs" or "DEADLINE_EXCEEDED: Deadline CallOptions was exceeded after Xs"Improvements
103bd4b)663c505) This updates default service config validation to accept numeric values represented as Number, not only Double. Common JSON parsers may deserialize integer-looking JSON values such as maxAttempts: 4 and backoffMultiplier: 2 as Integer, which previously caused defaultServiceConfig() to fail with IllegalArgumentException. The values are normalized to Double when copied into the validated service config, preserving the existing internal representation expected by the service config parsing code.56d2b25). Previously there was not a hint as to what gRPC was delayed on when the deadline was exceeded.4ec83df). This removes unnecessary log noise89aef90). This introduces the ChildChannelConfigurer API to allow intercepting and customizing the configuration (such as injecting interceptors or modifying credentials) of child channels created dynamically by load balancers.Dependencies
66c6ab1). If you need Netty 4.1 support, please file an issuec886f0a)064272c):Documentation
f94574e)Thanks to
tian__mi__mi@
codingkiddo@
Zhengcy05@
v1.82.4gRPC Java 1.82.4 Release Notes
Improvements
v1.82.3gRPC Java 1.82.3 Release Notes
The fixes that were supposed to go in this release were not included in the patch by mistake. Use 1.82.4 instead.
v1.82.2v1.82.1v1.82.0This 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.
Behavior Changes
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.Improvements
@ThreadSafeannotation 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.b38df6c). The main improvement here is not retaining the request Metadata for the life of the RPC. That means RPCs with larger request Metadata would see a larger benefit.f430131)cc0d1a8). This is most noticeable when there are many endpoints returned by EDS, but the LB policy only uses a few of them, like pick_first.324fce7). This reduces the per-RPC overhead of the gRFC A114 support added in v1.81.013b4b97). This preserves more information for failures communicating with the control plane.d92ca44)Bug Fixes
bb153a8).streamClosed()happens beforeserverCallStarted().GRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST=truewhen 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.ec10992). This should have no visible impact in normal use. It mostly just makes it easier to debug broken implementationsf4125c5)f021bef)New Features
?force-xdsquery parameter in thegoogle-c2presolver (#12760) (86fa860). This disables environment checks and uses xDS unconditionally. Please note that this feature has not yet seen comprehensive testing.Dependencies
ada087b)1dbb1a1(ec0a9c9). This fixed a rules_go incompatibility issue with Bazel 9.1. But it also greatly reduced the overall transitive dependencies, as the C++ grpc repo is no longer a dependency039ad77) add Bazel 9.1.0 to our CI matrix (17be0d3)8802dc3,da98b04)Thanks to
@becomeStar
@bengtsson1-flir
@jnowjack-lucidchart
@Kainsin
@kenkangxgwe
@mfperminov
@paulmurhy123
@schiemon
@therepanic
v1.81.1v1.81.0In 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
0675f70). DnsNameResolver ignores re-resolution requests on OpenJDK-like platforms if it has been too soon since the last DNS query because InetAddress.getAllByName() has a cache with a fixed entry lifetime, but this logic was disabled for Android which does not have that style of cache. Android’s cache uses the result TTL, which will rarely be less than 30 seconds. This change would probably be most noticeable when 1) changing to a different network (e.g., from wifi to mobile), 2) the server has different addresses for different networks, and 3) the app is not using AndroidChannelBuilder with anandroid.context.Context. For reference, it seems Chrome caches for 1 minutee39c38b). Previously each channel using the xds name resolver would create its own channel to communicate with the control plane. Now they share control plane channels, while still having separate RPCsBug Fixes
ManagedChannelOrphanWrappercould 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
0e39b29). This CallOption is copied by grpc-opentelemetry to thegrpc.client.call.customlabel as defined by gRFC A108. See also the gRPC OpenTelemetry Metrics guide (update in-progress)AdvancedTlsX509KeyManagerso that developers can now preserve and use key aliases when dynamically reloading TLS certificates. (#12686)Documentation
a3a9ffc) (#12726) (65ae2ef)3ed732f)Dependencies
16e17ab). Google-auth-library: 1.42.1, animal-sniffer: 1.27, assertj-core:3.27.7, error_prone_annotations:2.48.0, proto-google-common-protos:2.64.1, google-cloud-logging:3.23.10, jetty-http2-server:12.1.7, jetty-ee10-servlet:12.1.7, lincheck:3.4, opentelemetry-api:1.60.1, opentelemetry-exporter-prometheus:1.60.1-alpha, opentelemetry-gcp-resources:1.54.0-alpha, opentelemetry-sdk-extension-autoconfigure:1.60.1, opentelemetry-sdk-testing:1.60.1, robolectric:4.16.1, tomcat-embed-core:10.1.52, tomcat-embed-core9: 9.0.115,1528f80)Thanks to
v1.80.0API Changes
eae16b2)Bug Fixes
024fdd0)core: Fixed a race condition in RetriableStream where inFlightSubStreams counting could become inconsistent during concurrent retry and deadline events. This ensures that client calls (such as blockingUnaryCall) do not hang indefinitely and correctly receive a close signal. (#12649) (
73abb48)Improvements
470219f). This allows gRPC to avoid reflection, and the need to specify -keeps for various class’s constructors.Upgrade to protobuf 33.4 (#12615) (
50c18f1)31fdb6c)9903488)ac44e96)New Features
34dd290). This finishes the gRFC A113 pick_first: Weighted Random Shuffling supportThanks to
v1.79.0API Changes
core: Delete the never-used io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (#12580) (
738782f). 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 APIsopentelemetry: 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 (
4bbf8ee). 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 errorokhttp: Assert no pending streams before transport READY (#12566) (
ed6d175). 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 (
228fc8e). 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 (
f6d140f). Previously, localities with many endpoints or high endpoint weights could receive excess traffic. This is one part of gRFC A113 pick_first: Weighted Random ShuffleImprovements
core: Improve DEADLINE_EXCEEDED message for CallCreds delays (
ead532b). 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 (
a9f73f4). 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 compatiblecore: Catch Errors when calling complex config parsing code (
a535ed7). 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 channelcore: Implement LoadBalancer.Helper.createOobChannel() with the internals of createResolvingOobChannel() (
3915d02). 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.
f65127c) Experimental RFC 3986 target URI parsing mode (disabled by default)New Features
6b2f758), completing the remaining work in gRFC A96: OTel metrics for SubchannelsDependencies
protobuf: Upgrade Bazel protobuf to 33.1 (#12553) (
b61a8f4) and load java_proto_library from the protobuf repo (c7f3cdb)protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and grpc-proto versions (#12569)
Upgrade dependencies (#12588) (
6422092) 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
v1.78.0Bug Fixes
02e98a8). This fixes a race where RPCs could fail with "UNAVAILABLE: Channel shutdown invoked" even though they were created before channel.shutdown()8d49dc1)thisfrom BinderServerTransport's ctor (#12453) (89d77e0)55ae1d0). This fixes a regression since 1.75.0 triggered by CdsLb being converted to XdsDepManager. Without this fix, a second channel to the same target may hang when starting, causing DEADLINE_EXCEEDED, and unhang when the control plane delivers an update (e.g., endpoint address update)Improvements
f385add). We now have improved xDS error handling and this provides a clearer mechanism for the xDS server to report per-resource errors to the client, resulting in better error messages for debugging and faster detection of non-existent resources. This also improves the handling of all xDS-related data errors and the behavior of the xDS resource timer.26c1c13). Resets RLS request backoff timers when the Control plane channel state transitions to READY. Also when the backoff timer expires, instead of making a RLS request immediately, it just causes a picker update to allow making rpc again to the RLS target.4843256)283f103)bbc0aa3)9313e87)725ab22)cb73f21). Shared resources are internal to gRPC for sharing expensive objects across channels and servers, like threads. This reduces the chances of forming a deadlock, like seen with s2a ind50098f6dab2ce)f36defa). proto-google-common-protos to 2.63.1, google-auth-library to 1.40.0, error-prone annotations to 2.44.0, guava to 33.5.0-android, opentelemetry to 1.56.02f64092)d971072). Adds support forandroid:isolatedProcessServices and moves all security checks to the handshake, making subsequent transactions more efficient.New Features
58ae5f8).48a4288). The policy uses the namerandom_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 A5251611ba). Most service mesh workloads use mTLS, as described in gRFC A29. However, there are cases where it is useful for applications to use normal TLS rather than using certificates for workload identity, such as when a mesh wants to move some workloads behind a reverse proxy. The xDSCertificateValidationContextmessage (see envoyproxy/envoy#34235) has asystem_root_certsfield. In the gRPC client, if this field is present and theca_certificate_provider_instancefield is unset, system root certificates will be used for validation. This implements gRFC A82.51611ba). In service mesh environments, there are cases where intermediate proxies make it impossible to rely on mTLS for end-to-end authentication. These cases can be addressed instead by the use of service account identity JWT tokens. The xDS GCP Authentication filter provides a mechanism for attaching such JWT tokens as gRPC call credentials on GCP. gRPC already supports a framework for xDS HTTP filters, as described in gRFC A39. This release supports the GCP Authentication filter under this framework as described in gRFC A83.51611ba). gRPC supports getting routing configuration from an xDS server, as described in gRFCs A27 and A28. The xDS configuration can configure the client to rewrite the authority header on requests. This functionality can be useful in cases where the server is using the authority header to make decisions about how to process the request, such as when multiple hosts are handled via a reverse proxy. Note that this feature is solely about rewriting the authority header on data plane RPCs; it does not affect the authority used in the TLS handshake.As mentioned in gRFC A29, there are use-cases for gRPC that prohibit trusting the xDS server to control security-centric configuration. The authority rewriting feature falls under the same umbrella as mTLS configuration. As a result, the authority rewriting feature will only be enabled when the bootstrap config for the xDS server has
trusted_xds_serverin theserver_featuresfield.0567531). When using xDS credentials make SNI for the Tls handshake to be configured via xDS, rather than use the channel authority as the SNI, and make SAN validation to be able to use the SNI sent when so instructed via xDS. Implements gRFC A101.Documentation
da70387)28a6130)97695d5)Thanks to
v1.77.1Bug Fixes
v1.77.0API Changes
BinderChannelBuilder.bindAsUser()method, deprecated since 1.69 (#12401) (f96ce06)Bug Fixes
acbbf86). This fixes regression introduced in v1.68.1 causing a “IllegalStateException: No value present.” exception5e8af56). This should not impact many people as the code is disabled by default, behind two experimental environment variables6fc3fd0). This fixes the grpc-okhttp server incorrectly closing the connection withGOAWAY: too_many_pings63fdaac). SinceFileWatcherCertificateProviderisn'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 separateCertificateProviderfor handling system root certs that doesn't rely on theFileWatcherCertificateProvider.82f9b8e). This is needed when there isGcpAuthenticationFilterin the filter chain to make available the cluster resource inCallOptions.5b876cc)349a35a)4725ced)91f3f4d)Improvements
86e8b56)21696cd). A negative reference count could cause NullPointerExceptions, so when too many unrefs are detected it produces a SEVERE warning and prevents the reference count from going negative53cd1a2). This fixes a regression with Istio introduced in v1.73.0. This gives time for Istio’s new xDS field support to roll outConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.