[grpc-io] gRPC-Java v1.76.0 Released

[Abhishek Agrawal]

The v1.76.0 release is now available.

Bug Fixes

• xds: ClusterResolverLb has been converted to use XdsDepManager, which finishes the changes for gRFC A74 xDS Config Tears. This change should resolve some unnecessary reconnections introduced in v1.75.0 when using weighted_round_robin and maybe other policies.

• compiler: A fix has been implemented for the blockingV2 stub to mangle generated method names that conflict with java.lang.Object methods.

• servlet: A race condition in AsyncServletOutputStreamWriter has been fixed to prevent threads from getting stuck.

• servlet: An issue where AsyncContext.complete() was called multiple times, causing an IllegalStateException, has been resolved.

• binder: The REMOTE_UID is now required to hold the exact UID passed to the SecurityPolicy.

• binder: The server will now only accept post-setup transactions from the authorized server UID.

• util: AdvancedTlsX509TrustManager now errors with a message to say that files don’t exist instead of the previous “Files were unmodified before their initial update. Probably a bug.”

• android: A fix has been implemented for network change handling on API levels below 24.

Improvements

• api: Allocations of Attributes.Builder have been reduced. This mostly benefits attributes.toBuilder(), but that’s not expected to be visible in regular workloads.

• api: An empty array allocation in LoadBalancer.CreateSubchannelArgs.Builder has been avoided. It is a small optimization and is not expected to have any performance impact.

• servlet: A configurable methodNameResolver has been added to configure the mapping from servlet request paths to gRPC method name

• servlet: Avoid a race by increasing the AsyncContext timeout by 5 seconds. The gRPC Context timeout should trigger first

• xds: Pretty-print envoy.service.discovery.v3.Resource in debug logs

• bazel: The java/proto rules from rules_java/rules_proto are now used instead of native rules.

• bazel: Unnecessary direct build dependencies were removed from some targets

• netty: Support for the BCJSSE provider has been added in GrpcSslContexts.

• netty: Huffman coding in server response headers has been disabled; it was already disabled for client request headers

• netty: Include allow header for HTTP response code 405

• okhttp: Include allow header for HTTP response code 405

• binder: Error descriptions for ServiceConnection callbacks have been improved

• binder: Apps can now call SecurityPolicy.checkAuthorization() by PeerUid.

New Features

• stub: Trailers are now propagated in StatusException when thrown by BlockingClientCall.

• compiler: Support for macOS aarch64 with a universal binary has been added.

• opentelemetry: grpc.subchannel.* metrics as described in gRFC A94 OTel metrics for Subchannels have been added. grpc.disconnect_error will show as “unknown” until transports implement support

• binder: A NameResolver for Android's intent: URIs has been introduced.

• binder: A basic SocketStats with just the local and remote addresses has been added for channelz.

Documentation

• SECURITY.md: The documentation now describes how to use gcompat with LD_PRELOAD for Alpine.

• examples: The documentation now explains Bazel BCR releases and the git_override option.

Dependencies

• Upgraded Guava version to 33.4.8.
• The org.apache.tomcat:annotations-api dependency has been removed from the example

[Daniel Burrell]

Abhishek, I cannot see this grpc-java release in the bazel central registry, last release seen is 1.75.0: https://registry.bazel.build/modules/grpc-java

Also grpc is missing the last 2 releases too: https://registry.bazel.build/modules/grpc 

Is the BCR upload a separate process?

[Abhishek Agrawal]

Hi Daniel,
We have no process to update the BCR. To add a version someone sends a PR to https://github.com/bazelbuild/bazel-central-registry.
You might be interested in https://github.com/grpc/grpc-java/issues/12055.

Regards,

Abhishek Agrawal

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you must not disseminate, distribute or copy this e-mail. Please notify us on regul...@b2c2.net immediately if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/grpc-io/96d1373b-f1f3-40e4-ba16-46a373f01d3fn%40googlegroups.com.