build(deps): Bump grpc-java monorepo to v1.69.0 #999
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
d21f38a to
6769a1b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.66.0->1.69.01.66.0->1.69.01.66.0->1.69.0Release Notes
grpc/grpc-java (io.grpc:grpc-inprocess)
v1.69.0Compare Source
v1.69.0
New Features
LoadBalancers to specify an authority per-RPC.(#11631) (c167ead) CallOptions.withAuthority() has higher precedence.735b3f3) The soft limit is a lower size limit that fails an increasing percentage of RPCs as the Metadata size approaches the upper limit. This can be used as an “early warning” that the Metadata size is growing too largeGoogleDefaultChannelCredentials(#11634) (ba8ab79)20d09ce).grpc.xds.authorityis not yet availableBug Fixes
ListeneronAddresses toListener2continue to use onResult (#11666) (dae078c). This fixes a 1.68.1 "IllegalStateException: Not called from the SynchronizationContext" regression (#11662) that could be seen in certain custom NameResolversef1fe87). This fixes a 1.68.1 NullPointerException regression when a custom transportExecutor was provided to the channel and it did not have enough threads to run new tasksImprovements
java.time.Durationoverloads toCallOptions,AbstractStubmethods that take TimeUnit and a time value (#11562) (766b923)9176b55). This increases the timestamp precision from millisecondsAndroidComponentAddressspecify a target UserHandle (#11670) (e58c998)a5db67d)29dd9ba). The target s2a had been referenced by IO_GRPC_GRPC_JAVA_OVERRIDE_TARGETS but didn’t previously existb170334). This compatibility is on the source level. There is not a pre-built binary on Maven Central that supports proto lite921f88a). The class implements the deprecated v1alpha of the reflection protocol. Prefer ProtoReflectionServiceV1, which implements the v1 version of the reflection protocolDependencies
1993e68)1993e68)1993e68)1993e68)1993e68)664f1fc). This had been done for the Maven Central binaries in 1.63.0, but had been missed for Bazel buildsDocumentation
fe350cf)a79982c)Thanks to
@niloc132
@rockspore
@SreeramdasLavanya
@vinodhabib
v1.68.2Compare Source
Bug Fixes
Improvements
v1.68.1Compare Source
v1.68.0 was a mistake. This is the first release of version 1.68.x
Bug Fixes
Behavior Changes
4be69e3). This is the existing behavior in C core. Duplicate keys in objects are dangerous as which value takes effect is undefined. Previously, the last value was used3a6be9c). The transport uses two threads, but one is on-demand. If the executor provided tobuilder.transportExecutor()runs out of threads (e.g., it is a fixed-size thread pool), all transports can be wedged, unable to run on-demand tasks, until keepalive kills one of them. Two threads are now used when handshaking a new transport, and the transport will time out after 1 second with “Timed out waiting for second handshake thread” if two threads are unavailablemesh_idvalue fromCSM_MESH_IDenvironment variable, instead of getting it from bootstrap file (84d30af)Improvements
782a44a) (#11599) (e59ae5f). This is aio.grpc.Contextstorage override to store its state inio.opentelemetry.context.Context. Libraries should not add a dependency on this artifact, as applications can only have one storage override in their classpathio.grpc.s2a.S2AChannelCredentials1ded8af)b692b9d). This expands the class of bugs that will fail RPCs with the panic error, versus some undefined behaviorfa26a8b)StreamTracer.inboundMessageRead()now reports uncompressed message size when the message does not need compression (#11598) (2aae68e). Previously it always reported-1(unknown)62f4098)6f35422). This is especially helpful when using TLS but not running on AndroidUdsChannelBuilder, use fake IP instead of localhost (a908b5e). This avoids an unnecessary DNS lookupf3cf7c3)99be6e9)46c1b38)94a0a0d)GRPC_EXPERIMENTAL_ENABLE_OTEL_TRACINGenvironment variable totrueto enable tracing support inGrpcOpenTelemetry(#11409, #11477)(043ba55,421e237)Dependencies
2ff837a)Thanks to:
@Juneezee
@lgalfaso
@bestbeforetoday
@hlx502
@JoeCqupt
v1.68.0: MISTAKECompare Source
This was supposed to be v1.67.0, but there was a mistake during the release process. This has everything in v1.67.1, except for:
v1.67.1Compare Source
gRPC Java 1.67.1 Release Notes
There was no 1.67.0 release. There was a problem making the release and it went to Maven Central as 1.68.0 instead. This is a version-corrected release.
Improvements
90d0fab)e821d5e). This makes it clearer whether a leak is a gRPC leak or an application leak when the Detachable API is being used6a9bc3b)72a977b)6dbd1b9)d034a56)96a788a)0017c98)c29763d)10d6002). Previously, RLS configuration would not have been updatedBug Fixes
cc1cbe9)c63e354)f866c80). This change applies to all petiole load balancing policies. For regular usages that use dns name resolution, this is unlikely to matter as the default dns name resolver returns consistent addresses. But this might improve LB behavior for some custom load balancers1dae144)448ec4f)Dependencies
70ae832)75012a5)ff8e413)Thanks to
@Juneezee
@lujiajing1126
@JarvisCraft
@sunpe
Configuration
📅 Schedule: Branch creation - "every month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.