Bump the gradle-all group across 9 directories with 7 updates

[dependabot]

Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/async-http-api directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.
Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/entities directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.
Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/eternal-orchestrations directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.
Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/fan-out-fan-in directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.
Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/function-chaining directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.
Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/human-interaction directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.
Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/monitoring directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.
Bumps the gradle-all group with 7 updates in the /samples/durable-task-sdks/java/opentelemetry-tracing directory:

Package	From	To
ch.qos.logback:logback-classic	1.5.37	1.6.1
io.grpc:grpc-protobuf	1.82.1	1.83.0
io.grpc:grpc-stub	1.82.1	1.83.0
io.grpc:grpc-netty-shaded	1.82.1	1.83.0
io.opentelemetry:opentelemetry-api	1.63.0	1.64.0
io.opentelemetry:opentelemetry-sdk	1.63.0	1.64.0
io.opentelemetry:opentelemetry-exporter-otlp	1.63.0	1.64.0

Bumps the gradle-all group with 4 updates in the /samples/durable-task-sdks/java/sub-orchestrations directory: ch.qos.logback:logback-classic, io.grpc:grpc-protobuf, io.grpc:grpc-stub and io.grpc:grpc-netty-shaded.

Updates ch.qos.logback:logback-classic from 1.5.37 to 1.6.1

Release notes

Sourced from ch.qos.logback:logback-classic's releases.

Logback 1.6.1

2026-07-28 Release of logback version 1.6.1

• In TimeBasedRollingPolicy, when the file option is set, the intermediate file renamed before asynchronous compression now receives the target archive name without the compression suffix (e.g. .gz, .zip, .xz). Previously it used a nanotime-based .tmp suffix. This makes the file easier to identify if compression fails during rollover. (See also the following paragraph.)

• On GZ, ZIP, or XZ compression failure, the original (uncompressed) log file is no longer deleted. Compression strategies now delete the source file only after successful compression and emit a warning that the original was left intact.

• ConsoleAppender with now probes JLine's org.jline.jansi.AnsiConsole first and falls back to the legacy FuseSource org.fusesource.jansi.AnsiConsole class. This keeps ANSI coloring working after Jansi moved under the JLine project. The optional org.jline:jansi-core artifact is declared as a dependency alongside the existing FuseSource jansi dependency. A preferredJansiClassName property was added for tests. This issue was reported in issues/1043 by seonwoo_jung who also provided the relevant PR.

• LayoutWrappingEncoder now reports an error at start() when no layout is set and guards encode() against a null layout. Previously, a missing layout (for example after an ignored // branch) allowed the encoder to start and then fail with a NullPointerException on every event, resulting in silent log loss. This issue was reported in issues/1046 by seonwoo_jung who also provided the relevant PR.

• FileCollisionAnalyser now detects file collisions involving nested appenders of SiftingAppender. When the nested file or fileNamePattern does not textually reference the discriminator key (e.g. ${userId}), a warning is issued at configuration time naming the appender, the key, and the shared target. This closes a gap where statically declared file appenders were checked but sifted nested appenders were not. This enhancement was contributed in [PR #1041](qos-ch/logback#1041) by seonwoo_jung.

• More defensive handling in SyslogOutputStream and SyslogAppenderBase: the close() method now ensures that resources are closed, writes and flushes check that the underlying resources are in a valid state and fallback to no-op otherwise.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 57759f433000a133088ef0441038963134437fbd associated with the tag v_1.6.1. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

• See https://logback.qos.ch/news.html#1.6.1 for the original text.

Logback 1.6.0

2026-07-23 Release of logback version 1.6.0

• Removed certain deprecated variables, methods, and classes. For the list of removed members see release_1.6.0.txt.

• In AsyncAppenderBase, the put(ILoggingEvent) method now has the protected modifier to allow access from derived classes. This change was requested by Thomas Skjølberg in pr#1053.

• Bump SLF4J dependency to version 2.0.18.

• See also the overview of the 1.6.x series.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit b07adf36019b51a10f824fdd94009985c587b1d3 associated with the tag v_1.6.0. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Logback 1.5.38

2026-07-09 Release of logback version 1.5.38

• In HardenedObjectInputStream, fixed a typo preventing Throwable objects from being white-filtered. This issue was reported in [PR #1045](qos-ch/logback#1045) by t0rchwo0d.

• A bitwise identical binary of this version can be reproduced by building from source code at commit d04984a41fce42977466f45a2f076f0ee5cc4207 associated with the tag v_1.5.38. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Commits

• 57759f4 prepare release 1.6.1
• 175f99f fix imports
• 4b8773e add compressionFailureLeavesOriginalFileIntact test for XZ compression
• cafaf11 do not delete original file if compression fails
• ee50125 let the temporary file before compression be target file without the .gz or ....
• 5626acc minor refactoring
• d97da4f minor refactoring
• 159c045 more defensive coding in SyslogOutputStream and in SyslogAppenderBase
• 9427d6b slight refactoring for clarity
• 79c4179 slight refactoring
• 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.3

gRPC Java 1.82.3 Release Notes

Improvements

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

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

gRPC Java 1.82.3 Release Notes

Improvements

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

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

gRPC Java 1.82.3 Release Notes

Improvements

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

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

gRPC Java 1.82.3 Release Notes

Improvements

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

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

gRPC Java 1.82.3 Release Notes

Improvements

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

Updates ch.qos.logback:logback-classic from 1.5.37 to 1.6.1

Release notes

Sourced from ch.qos.logback:logback-classic's releases.

Logback 1.6.1

2026-07-28 Release of logback version 1.6.1

• In TimeBasedRollingPolicy, when the file option is set, the intermediate file renamed before asynchronous compression now receives the target archive name without the compression suffix (e.g. .gz, .zip, .xz). Previously it used a nanotime-based .tmp suffix. This makes the file easier to identify if compression fails during rollover. (See also the following paragraph.)

• On GZ, ZIP, or XZ compression failure, the original (uncompressed) log file is no longer deleted. Compression strategies now delete the source file only after successful compression and emit a warning that the original was left intact.

• ConsoleAppender with now probes JLine's org.jline.jansi.AnsiConsole first and falls back to the legacy FuseSource org.fusesource.jansi.AnsiConsole class. This keeps ANSI coloring working after Jansi moved under the JLine project. The optional org.jline:jansi-core artifact is declared as a dependency alongside the existing FuseSource jansi dependency. A preferredJansiClassName property was added for tests. This issue was reported in issues/1043 by seonwoo_jung who also provided the relevant PR.

• LayoutWrappingEncoder now reports an error at start() when no layout is set and guards encode() against a null layout. Previously, a missing layout (for example after an ignored // branch) allowed the encoder to start and then fail with a NullPointerException on every event, resulting in silent log loss. This issue was reported in issues/1046 by seonwoo_jung who also provided the relevant PR.

• FileCollisionAnalyser now detects file collisions involving nested appenders of SiftingAppender. When the nested file or fileNamePattern does not textually reference the discriminator key (e.g. ${userId}), a warning is issued at configuration time naming the appender, the key, and the shared target. This closes a gap where statically declared file appenders were checked but sifted nested appenders were not. This enhancement was contributed in [PR #1041](qos-ch/logback#1041) by seonwoo_jung.

• More defensive handling in SyslogOutputStream and SyslogAppenderBase: the close() method now ensures that resources are closed, writes and flushes check that the underlying resources are in a valid state and fallback to no-op otherwise.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 57759f433000a133088ef0441038963134437fbd associated with the tag v_1.6.1. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

• See https://logback.qos.ch/news.html#1.6.1 for the original text.

Logback 1.6.0

2026-07-23 Release of logback version 1.6.0

• Removed certain deprecated variables, methods, and classes. For the list of removed members see release_1.6.0.txt.

• In AsyncAppenderBase, the put(ILoggingEvent) method now has the protected modifier to allow access from derived classes. This change was requested by Thomas Skjølberg in pr#1053.

• Bump SLF4J dependency to version 2.0.18.

• See also the overview of the 1.6.x series.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit b07adf36019b51a10f824fdd94009985c587b1d3 associated with the tag v_1.6.0. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Logback 1.5.38

2026-07-09 Release of logback version 1.5.38

• In HardenedObjectInputStream, fixed a typo preventing Throwable objects from being white-filtered. This issue was reported in [PR #1045](qos-ch/logback#1045) by t0rchwo0d.

• A bitwise identical binary of this version can be reproduced by building from source code at commit d04984a41fce42977466f45a2f076f0ee5cc4207 associated with the tag v_1.5.38. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Commits

• 57759f4 prepare release 1.6.1
• 175f99f fix imports
• 4b8773e add compressionFailureLeavesOriginalFileIntact test for XZ compression
• cafaf11 do not delete original file if compression fails
• ee50125 let the temporary file before compression be target file without the .gz or ....
• 5626acc minor refactoring
• d97da4f minor refactoring
• 159c045 more defensive coding in SyslogOutputStream and in SyslogAppenderBase
• 9427d6b slight refactoring for clarity
• 79c4179 slight refactoring
• 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.3

gRPC Java 1.82.3 Release Notes

Improvements

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

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

  Description has been truncated

[Copilot]

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Updates dependency versions across the Java Durable Task SDK samples to newer releases (gRPC, Logback, and OpenTelemetry in tracing sample).

Changes:

• Bump gRPC version from 1.82.1 to 1.83.0 across multiple Java sample projects.
• Upgrade Logback Classic from 1.5.37 to 1.6.1 across multiple Java sample projects.
• Bump OpenTelemetry version from 1.63.0 to 1.64.0 in the tracing sample.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
samples/durable-task-sdks/java/sub-orchestrations/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample.
samples/durable-task-sdks/java/opentelemetry-tracing/build.gradle	Updates gRPC + OpenTelemetry + Logback versions for tracing sample.
samples/durable-task-sdks/java/monitoring/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample.
samples/durable-task-sdks/java/human-interaction/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample.
samples/durable-task-sdks/java/function-chaining/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample.
samples/durable-task-sdks/java/fan-out-fan-in/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample.
samples/durable-task-sdks/java/eternal-orchestrations/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample.
samples/durable-task-sdks/java/entities/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample (Java 11).
samples/durable-task-sdks/java/async-http-api/build.gradle	Updates shared dependency versions (gRPC, Logback) for this sample.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.