Update all non-major dependencies #336
Merged
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:
2.7.1
->2.7.2
2.7.1
->2.7.2
2.25.3
->2.25.4
1.69.1
->1.70.0
1.69.1
->1.70.0
1.69.1
->1.70.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
googleapis/google-api-java-client (com.google.api-client:google-api-client)
v2.7.2
Compare Source
Bug Fixes
googleapis/java-datastore (com.google.cloud:google-cloud-datastore)
v2.25.4
Compare Source
Dependencies
grpc/grpc-java (io.grpc:grpc-netty)
v1.70.0
Compare Source
Bug 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.target
label 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
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.