Skip to content

build(deps): bump the minor-and-patch group across 1 directory with 5 updates - #89

Open
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/maven/services/user-service/dev/minor-and-patch-33813c9b73
Open

build(deps): bump the minor-and-patch group across 1 directory with 5 updates#89
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/maven/services/user-service/dev/minor-and-patch-33813c9b73

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 12, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the minor-and-patch group with 5 updates in the /services/user-service directory:

Package From To
io.grpc:grpc-netty-shaded 1.82.1 1.83.0
io.grpc:grpc-protobuf 1.82.1 1.83.0
io.grpc:grpc-stub 1.82.1 1.83.0
io.grpc:grpc-services 1.82.1 1.83.0
io.grpc:grpc-testing 1.82.1 1.83.0

Updates io.grpc:grpc-netty-shaded from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-netty-shaded'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"
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

Updates io.grpc:grpc-protobuf from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-protobuf'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"
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

Updates io.grpc:grpc-stub from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-stub'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"
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

Updates io.grpc:grpc-services from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-services'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"
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

Updates io.grpc:grpc-testing from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-testing'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"
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

Updates io.grpc:grpc-protobuf from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-protobuf'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"
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

Updates io.grpc:grpc-stub from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-stub'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"
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

Updates io.grpc:grpc-services from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-services'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"
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

Updates io.grpc:grpc-testing from 1.82.1 to 1.83.0

Release notes

Sourced from io.grpc:grpc-testing'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) (c886f0a0...

    Description has been truncated

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Jul 12, 2026
@dependabot
build(deps): bump the minor-and-patch group across 1 directory with 5…
18e9f6b 
… updates

Bumps the minor-and-patch group with 5 updates in the /services/user-service directory:

| Package | From | To |
| --- | --- | --- |
| [io.grpc:grpc-netty-shaded](https://github.com/grpc/grpc-java) | `1.82.1` | `1.83.0` |
| [io.grpc:grpc-protobuf](https://github.com/grpc/grpc-java) | `1.82.1` | `1.83.0` |
| [io.grpc:grpc-stub](https://github.com/grpc/grpc-java) | `1.82.1` | `1.83.0` |
| [io.grpc:grpc-services](https://github.com/grpc/grpc-java) | `1.82.1` | `1.83.0` |
| [io.grpc:grpc-testing](https://github.com/grpc/grpc-java) | `1.82.1` | `1.83.0` |



Updates `io.grpc:grpc-netty-shaded` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-protobuf` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-stub` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-services` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-testing` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-protobuf` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-stub` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-services` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

Updates `io.grpc:grpc-testing` from 1.82.1 to 1.83.0
- [Release notes](https://github.com/grpc/grpc-java/releases)
- [Commits](grpc/grpc-java@v1.82.1...v1.83.0)

---
updated-dependencies:
- dependency-name: io.grpc:grpc-netty-shaded
  dependency-version: 1.82.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-protobuf
  dependency-version: 1.82.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-protobuf
  dependency-version: 1.82.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-services
  dependency-version: 1.82.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-services
  dependency-version: 1.82.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-stub
  dependency-version: 1.82.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-stub
  dependency-version: 1.82.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-testing
  dependency-version: 1.82.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: io.grpc:grpc-testing
  dependency-version: 1.82.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps): bump the minor-and-patch group in /services/user-service with 5 updates build(deps): bump the minor-and-patch group across 1 directory with 5 updates Jul 26, 2026
@dependabot
dependabot Bot force-pushed the dependabot/maven/services/user-service/dev/minor-and-patch-33813c9b73 branch from af8d6d4 to 18e9f6b Compare July 26, 2026 01:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants