build(deps): bump io.grpc:grpc-core from 1.81.0 to 1.83.0 in /sdk/java/grpc

[dependabot]

Bumps io.grpc:grpc-core from 1.81.0 to 1.83.0.

Release notes

Sourced from io.grpc:grpc-core's releases.

v1.83.0

gRPC Java 1.83.0 Release Notes

API Changes

• api: Turn on RFC 3986 parsing by default and update javadoc. (4456721328)
• api: Add Grpc.newChannelBuilder accepting NameResolverRegistry (#11901) (2b86f8f42f). 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 (3018ce341c). v1.82.0 enabled TLS 1.3 for clients; this does the same for servers
• xds: enable orca to lrs propagation by default (#12836) (1e85674a40) 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) (c8079eed98). This only has an effect when using aggregate clusters
• xds: Hold parsed service config in CdsUpdate (3db3235ebd). 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 (d49c0b15d8). 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 (103bd4b852)
• core: normalize service config number values (#12826) (663c505dbd) 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 (56d2b25eb5). 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 (4ec83df1eb). This removes unnecessary log noise
• core: Enable child channel plugins (#12578) (89aef90d52). 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 (66c6ab1da6). If you need Netty 4.1 support, please file an issue
• Upgrade codegen plugin to C++ Protobuf 35.1 (#12876) (c886f0a06b)
• Upgrade various dependencies (064272c61d):
  • 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) (f94574eff7)

Thanks to

tian__mi__mi@
codingkiddo@
Zhengcy05@

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

... (truncated)

Commits

• 8ab6e0a Bump version to 1.83.0
• 33ad6a4 Update README etc to reference 1.83.0
• 17d5bd6 Revert "enable child channel plugins (#12578)" (v1.83.x backport) (#12913)
• 89aef90 enable child channel plugins (#12578)
• fd971d1 fix: configure Undertow test entity size (#12892)
• c8079ee xds: Move backend service label plumbing to CDS (#12882)
• 53ebe2d xds: Fix half-close race condition in ext-proc client interceptor (#12888)
• 0cf5239 xds: Implementation of Unified Matcher (#12640)
• 036c7f0 xds: Refactor to allow common code usage between the ext_proc client and serv...
• d49c0b1 Revert "xds: reuse GrpcXdsTransport and underlying gRPC channel to the same x...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)