fix(deps): update dependency io.grpc:grpc-bom to v1.52.1

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.grpc:grpc-bom	1.51.1 -> 1.52.1

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

grpc/grpc-java

v1.52.1

Compare Source

Bug Fixes

• xds: Fix an internal bug in xds resource subscription that might cause xds stream not accepting response update for that resource type entirely. (#​9810)

v1.52.0

Compare Source

gRPC Java 1.52.0 Release Notes

grpc-xds starting with 1.51.0 had a regression where resources might stop receiving updates. The trigger could happen hours or days after the binary had started. xDS users should avoid this release and use 1.50.x until patch releases with the fix are available. https://github.com/grpc/grpc-java/pull/9809

API Changes

• Fix CallOptions to be properly @Immutable (#​9689)
• binder: Promote out of experimental status (#​9669). Much of the API is now stable

New Features

• xds: Support localities in multiple priorities (#​9683)
• xds: Log xDS node ID with verbosity INFO when environment variable GRPC_LOG_XDS_NODE_ID=true (#​9731)

Examples

• Add examples for name resolver and load balancer (#​9700)
• Swap to ChannelCredentials/ServerCredentials API, as it is preferred

Bug Fixes

• xds:Fix ConcurrentModificationException in PriorityLoadBalancer (#​9728)
• ManagedChannelImpl.SubchannelImpl fix args check to avoid NPE (#​9651)
• okhttp: Add missing server support for TLS ClientAuth (#​9711)
• binder: Ensure the security interceptor is always closest to the actual transport (#​9716)
• bazel: Include @​Generated dep for autovalue. This fixes builds of xds and rls using Java 9+
• xds: Nack xds response when weighted cluster total weight sums zero (#​9738)
• core: Fix a bug about a retriable stream lifecycle. It stops using the call executor resource in a retriable stream when the client call is closed, thus preventing potential channel panics. (#​9626)

Behavior Changes

• binder: Set default idle timeout to 60 seconds, and enable "strict lifecycle management". (#​9486)
• xds: Limit ring hash max size to 4K instead of 8M (#​9709). RingHashOptions.setRingSizeCap() can increase the limit
• binder: Set default idle timeout to 60 seconds, and add BinderChannelBuilder.strictLifecycleManagement() which disables idle timeout and prevents it from being changed (#​9486). Disabling idle timeout can be useful to find bugs in applications that fail to promptly shut down the channel and are particularly sensitive to keeping Binder instances alive.
• bazel: Replace ctx.host_configuration.host_path_separator with ctx.configuration.host_path_separator (#​9742). This changes no behavior today, but improves future compatibility with newer versions of Bazel
• xds: Refactor internal logics about LDS and CDS resource handling. It may cause minor log line changes about corresponding RDS and EDS subscriber event notification, but it should not change xds name resolution and LB behavior. (#​9724)

Dependencies

Acknowledgement

@​RapperCL
@​Smityz
@​pandaapo

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[forking-renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication