Update all non-major dependencies - #336
Conversation
ghost
left a comment
There was a problem hiding this comment.
Hi team,
I'm currently reviewing this pull request and will provide feedback shortly. In the meantime, here's a summary for you and other reviewers to quickly get up to speed:
This pull request, submitted by Renovate Bot, aims to update several non-major dependencies to their latest versions. The changes are primarily focused on updating version numbers in the pom.xml files.
Here's a breakdown of the changes:
-
Dependency Updates:
com.google.api-client:google-api-client: Updated from2.7.1to2.7.2com.google.api-client:google-api-client-appengine: Updated from2.7.1to2.7.2com.google.cloud:google-cloud-datastore: Updated from2.25.3to2.25.4io.grpc:grpc-netty,io.grpc:grpc-protobuf,io.grpc:grpc-api: Updated from1.69.1to1.70.0
-
Affected Files:
applications/proberapp/pom.xml(Line 129:google-cloud-datastoreversion updated)pom.xml(Line 69:io.grpcversion updated; Lines 328 and 333:google-api-clientandgoogle-api-client-appengineversions updated)
The pull request includes release notes detailing the changes in each updated dependency. Some dependencies could not be fully analyzed by the bot, so please review the Dependency Dashboard for more information.
The Renovate bot has configured this PR for automatic rebasing and will recreate it if closed unmerged. Manual merge is required.
And now, a little haiku to lighten the mood:
Version numbers rise,
Code refreshed, bugs may flee,
Smooth update complete.
ghost
left a comment
There was a problem hiding this comment.
This pull request updates several non-major dependencies, which is good practice for maintaining security and stability. The provided details about each update (change, age, adoption, passing, confidence) are helpful. However, I recommend adding a section to the description summarizing the key changes introduced by these dependency updates, especially any potential breaking changes or new features that might require code adjustments. This will help reviewers and future maintainers understand the impact of these changes more easily.
I also noticed a warning about some dependencies not being looked up. It's crucial to investigate this and ensure all dependencies are accounted for on the Dependency Dashboard. Unresolved dependencies can lead to build issues or unexpected runtime behavior.
This PR contains the following updates:
2.7.1->2.7.22.7.1->2.7.22.25.3->2.25.41.69.1->1.70.01.69.1->1.70.01.69.1->1.70.0Warning
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.2Compare Source
Bug Fixes
googleapis/java-datastore (com.google.cloud:google-cloud-datastore)
v2.25.4Compare Source
Dependencies
grpc/grpc-java (io.grpc:grpc-netty)
v1.70.0Compare 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.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
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.