Update gRPC and Netty

[solrbot]

This PR contains the following updates:

Package	Type	Update	Change
io.netty:netty-tcnative-classes	dependencies	patch	2.0.79.Final → 2.0.81.Final
io.netty:netty-tcnative-boringssl-static (source)	dependencies	patch	2.0.79.Final → 2.0.81.Final
io.netty:netty-transport-native-epoll (source)	dependencies	patch	4.2.15.Final → 4.2.17.Final
io.netty:netty-transport-classes-epoll (source)	dependencies	patch	4.2.15.Final → 4.2.17.Final
io.netty:netty-handler (source)	dependencies	patch	4.2.15.Final → 4.2.17.Final
io.netty:netty-codec-http (source)	dependencies	patch	4.2.15.Final → 4.2.17.Final
io.netty:netty-bom (source)	dependencies	patch	4.2.15.Final → 4.2.17.Final
io.grpc:grpc-util	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-stub	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-protobuf-lite	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-protobuf	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-netty	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-core	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-context	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-bom	dependencies	minor	1.82.0 → 1.83.1
io.grpc:grpc-api	dependencies	minor	1.82.0 → 1.83.1

---

Release Notes

grpc/grpc-java (io.grpc:grpc-util)

v1.83.1

gRPC Java 1.83.1 Release Notes

Improvements

• netty: Fix client-initiated stream limit bypass in NettyServerHandler (#​12942). Enforces the limit proactively at startup without waiting for SETTINGS_ACK
• core: Coalesce Contiguous Small Buffers for ReadableBuffer (#​12944)

v1.83.0

gRPC Java 1.83.0 Release Notes

API Changes

• api: Turn on RFC 3986 parsing by default and update javadoc. (4456721)
• api: Add Grpc.newChannelBuilder accepting NameResolverRegistry (#​11901) (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

• okhttp: enable TLS 1.3 for servers on Android (3018ce3). v1.82.0 enabled TLS 1.3 for clients; this does the same for servers
• xds: enable orca to lrs propagation by default (#​12836) (1e85674) Enables xDS configuration to control which fields get propagated from ORCA backend metric reports to LRS load reports as per gRFC A85
• xds: Use leaf cluster name for backend service label in metrics, instead of aggregate cluster name (#​12882) (c8079ee). This only has an effect when using aggregate clusters
• xds: Hold parsed service config in CdsUpdate (3db3235). Previously, modifications to LoadBalancerRegistry could cause failures in the LB tree
• xds: Revert "xds: reuse connections to the control plane across channels" added in 1.81.0 (d49c0b1). 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

• api: Move attributes to the end of ResolvedAddresses.toString(), for better legibility (103bd4b)
• core: normalize service config number values (#​12826) (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.
• core: DEADLINE_EXCEEDED before initial name resolution completes will now mention “name_resolver” in the error description (56d2b25). Previously there was not a hint as to what gRPC was delayed on when the deadline was exceeded.
• netty: Reduce TcpMetrics log from INFO to FINE (4ec83df). This removes unnecessary log noise
• core: Enable child channel plugins (#​12578) (89aef90). 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

• Upgrade to Netty 4.2.15 (66c6ab1). If you need Netty 4.1 support, please file an issue
• Upgrade codegen plugin to C++ Protobuf 35.1 (#​12876) (c886f0a)
• Upgrade various dependencies (064272c):
  • gson to 2.14.0
  • guava to 33.6.0
  • cel-java to 0.13.0
  • protobuf-java to 3.25.9
  • error-prone-annotations to 2.50.0
  • opentelemetry to 1.63.0

Documentation

• Document how to build with Bazel and introduce bazel support for building android and binder (#​12811) (f94574e)

Thanks to

tian__mi__mi@
codingkiddo@
Zhengcy05@​

v1.82.4

gRPC Java 1.82.4 Release Notes

Improvements

• netty: Fix client-initiated stream limit bypass in NettyServerHandler (#​12941). Enforces the limit proactively at startup without waiting for SETTINGS_ACK
• core: Coalesce Contiguous Small Buffers for ReadableBuffer (#​12943)

v1.82.3

gRPC 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.2

• 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_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"

v1.82.1

• protoc-gen-grpc-java: Fix missing osx-x86_64 binary (#​12878). This fixes a regression in v1.82.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on the first day of the month"
• Automerge
  • At any time (no schedule defined)

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot

[solrbot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[epugh]

Not sure why this changed... it all appears magic...

[epugh]

@janhoy is this another PR from before we started having Solrbot only open things on the 1st of the month?

[epugh]

Okay, tests all pass.... Will look to merge this tomorrow.