Repository navigation
Conversation
|
🤖 AI text below 🤖 (reviewed by Nick Shanin) Prepared fix: compare this PR's head with the repair branch License metadata is missing for four artifacts this PR pulls in, and the PR's own precommit run shows it: Verification and limitsThe license texts come from the exact upstream sources. The CEL license is the LICENSE file from google/cel-java v0.13.1 (SHA-256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30, same file for all three artifacts); the ThreeTen Extra license is META-INF/LICENSE.txt from its Maven Central JAR (SHA-256 decba4464d41e505481403488af67078ce7078eacb164ccf78146c2d12e1206e). Neither artifact supplies a NOTICE, so the notice companions are empty, following the existing api-common, gson and threetenbp convention in solr/licenses. This is a static provenance audit: the texts were compared against the upstream sources and the hashes recorded, but no Gradle run has been executed at the repair head yet. The failing precommit run linked above, at this PR's current head, is the before evidence. The repair is one commit on top of this PR's head, so it fast-forwards: You're welcome to take the commits or adapt the changes. |
This PR contains the following updates:
4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final4.2.15.Final→4.2.19.Final1.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.11.82.1→1.85.14.35.1→4.36.24.35.1→4.36.2Release Notes
grpc/grpc-java (io.grpc:grpc-xds)
v1.85.1What's Changed
v1.85.0gRPC Java 1.85.0 Release Notes
API Changes
e9a8c2b). High-cardinality metadata values provide little compression benefit and can churn the server's dynamic HPACK table. AddsNettyChannelBuilder.neverIndexMetadataKey()andneverIndexMetadataKeys() so callers can mark selected outbound metadata keys for HPACK's never-indexed literal representation.hasPermissions()toSecurityPoliciesand deprecate thePackageManagerversion.Behavior Changes
5fda0c7). It now accepts a port of 0 in the LDS listener address as matching any port.Bug Fixes
e58489f). Fixes a bug that caused empty payloads on retry attempts for regular xDS channels.fc43144). Because of a bug in the config selector, when ManagedChannel entered IDLE state due to resource deletion on the xDS control plane, the channel stayed stuck in IDLE state even after the resource came back online and a new rpc was executed.b3ae801). When a server or proxy sent a GOAWAY with an unrecognized HTTP/2 error code, such as 70007 from Apache httpd, Netty transport clients loggedNullPointerException: Http2Error cannot be null for GOAWAYand RPCs could hang until their deadline. Such codes are now treated as INTERNAL_ERROR, so the transport shuts down cleanly.Improvements
2858db2). This configures HTTPS endpoint identification in GrpcSslContexts and updates ClientTlsHandler to preserve an explicit empty-string opt-out. A null algorithm still falls back to HTTPS, retaining hostname verification for custom contexts that do not select an algorithm.c9ee3f8).java_grpc_libraryandjava_lite_grpc_librarynow invoke protoc through Protobuf'sproto_lang_toolchaininstead of always using@com_google_protobuf//:protoc. They now use the same protoc and protoc options asjava_proto_library.New Features
dd00881). This adds triggerEvent/onEvent APIs toServerCallandServerCall.Listener. This allows events to be triggered on theServerCalland be delivered as a listener callback.Dependencies
9799887)61b910b). netty-tcnative remains at 2.0.81.Documentation
893eb70)Thanks to
@kkalin68
@petedmarsh
v1.84.3Bug Fixes
v1.84.1v1.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.2Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot