fix(deps): Update grpc-java monorepo to v1.70.0 #319
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
![kodiakhq[bot]](https://avatars.githubusercontent.com/in/29196?s=60&v=4){kind=small}
kodiakhq bot
pushed a commit
that referenced
this pull request
Feb 3, 2025
🤖 I have created a release *beep* *boop* --- ## [0.0.38](v0.0.37...v0.0.38) (2025-02-03) ### Bug Fixes * **deps:** Update dependency gradle to v8.12.1 ([#314](#314)) ([0b29ccd](0b29ccd)) * **deps:** Update dependency io.cloudquery:plugin-pb-java to v0.0.30 ([#321](#321)) ([b875a01](b875a01)) * **deps:** Update dependency nl.jqno.equalsverifier:equalsverifier to v3.18.1 ([#317](#317)) ([c1d543d](c1d543d)) * **deps:** Update dependency org.assertj:assertj-core to v3.27.3 ([#318](#318)) ([f321084](f321084)) * **deps:** Update eclipse-temurin Docker tag to v21.0.6_7-jre ([#315](#315)) ([c888a38](c888a38)) * **deps:** Update grpc-java monorepo to v1.70.0 ([#319](#319)) ([97b3b6c](97b3b6c)) * **deps:** Update mockito monorepo to v5.15.2 ([#320](#320)) ([5110a9a](5110a9a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.68.2->1.70.01.68.2->1.70.01.68.2->1.70.01.68.2->1.70.01.68.2->1.70.0Release Notes
grpc/grpc-java (io.grpc:grpc-inprocess)
v1.70.0Bug Fixes
8ea3629). Violations would only have triggered on API level 23 and earlier, and the violations fixed here were highly unlikely to be triggeredebe2b48). This fixes a regression introduced in 1.64.0. The regression should have caused failures on API level 23 and earlier when a StatusRuntimeException or StatusException was created. However, for unknown reasons tests on old devices didn’t notice issuesa0982ca). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix65b32e6)1cf1927). This (along with6c12c2b) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b)e8ff6da). They were previously required to be strings6516c73). This fixes the error “Incorrect number of required labels provided. Expected: 4” introduced in 1.69.0f8f6139). This fixes clients treating large max_requests as “no requests” and failing all requestsImprovements
0b2d440)ea8c31c)805cad3)1126a8e)ef7c2d5)1edc4d8). Not used actively, but this adds validation. The validation is unlikely to fail but may reject invalid resources.ebb43a6). This only impacts thegrpc.targetlabel ingrpc.xds_client.*metrics. Previously the empty string was used7f9c1f3). This only matters when debug logging is enabledDocumentation
f1109e4)c96e926)5e8abc6)Dependencies
8a5f777)Thanks to
v1.69.1Bug Fixes
a0982ca). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix1cf1927). This (along with6c12c2b) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b)e8ff6da). They were previously required to be stringsf8f6139). This fixes clients treating large max_requests as “no requests” and failing all requests6516c73). This fixes the error “Incorrect number of required labels provided. Expected: 4” introduced in 1.69.0v1.69.0v1.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.3Bug Fixes
a0982ca). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix1cf1927). This (along with6c12c2b) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b)e8ff6da). They were previously required to be stringsf8f6139). This fixes clients treating large max_requests as “no requests” and failing all requestsConfiguration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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 these updates again.
This PR has been generated by Renovate Bot.