deps: Update Non-major dependencies #601
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
force-pushed
the
renovate/non-major-dependencies
branch
from
4732838 to
91cce8a
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/non-major-dependencies
branch
2 times, most recently
from
827a78f to
fbc703a
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependencies
branch
4 times, most recently
from
19d131d to
6bc791c
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependencies
branch
3 times, most recently
from
040f219 to
2234b66
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependencies
branch
3 times, most recently
from
ec0157b to
6b84749
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependencies
branch
2 times, most recently
from
cdd7646 to
143e6b2
Compare
renovate-bot
force-pushed
the
renovate/non-major-dependencies
branch
from
143e6b2 to
1f6bc4f
Compare
enocom
approved these changes
Feb 10, 2025
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:
5.11.3->5.11.45.11.3->5.11.45.11.3->5.11.45.11.3->5.11.42.49.0->2.51.02.58.0->2.60.01.69.0->1.70.00.32.0->0.35.00.43.0->0.46.03.40.0->3.42.01.79->1.801.79->1.802.35.1->2.36.042.7.4->42.7.51.12.2->1.14.2Release Notes
googleapis/sdk-platform-java (com.google.api.grpc:proto-google-common-protos)
v2.51.0Features
Bug Fixes
Dependencies
1e42bbe(#3417) (0f4ef19)3bab9f2(#3447) (ccf7eac)cdfb386(#3418) (2559ff8)93740d5(#3280) (f987db5)6662ddc(#3421) (dec5de0)8230b4e(#3448) (e53199b)ae0a72f(#3452) (331bacf)f3fbbab(#3419) (343a029)Documentation
README.md(#3388) (2ac86de)v2.50.0Compare Source
Features
java.timeto java-core (#3330) (f202c3b)java.timemethods (#3321) (b21c9a4)Bug Fixes
Dependencies
Documentation
grpc/grpc-java (io.grpc:grpc-bom)
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.0googleapis/google-cloud-java (com.google.cloud:google-cloud-alloydb-connectors-bom)
v0.35.0: 0.35.0Compare Source
Misc
Bigtable
Bigquery
Storage
Speech
Core
Logginig
Firestore
Datastore
Dns
v0.34.0: 0.34.0Compare Source
BigQuery
Compute
Datastore
Dependencies/build logic
Firestore
Logging
Storage
Cross-API
Readmes/other docs
v0.33.0: 0.33.0Compare Source
Big Query
Firestore
Logging
NIO
Pub/Sub
Spanner
Cross-API
New Clients
Dependencies/build logic
Readmes/other docs
Note
We have started a new reference page which details breaking changes at https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/CHANGES.md . This will be updated to reflect breaking changes in a more descriptive way going forward, and will be the best place to consult for finding out how to adjust to the breaking changes in each release.
google/error-prone (com.google.errorprone:error_prone_annotations)
v2.36.0: Error Prone 2.36.0Compare Source
Changes:
ErrorProneScannerfor AST nodes introduced after Java 11 (e5fd194)--should-stop=ifError=FLOWis set when using the-Xpluginintegration (e71db1f)New checks:
DuplicateBranches: Discourage conditional expressions and if statements where both branches are the sameRedundantControlFlow: Reports redundantcontinuestatements.Closed issues: #4633, #4646
Full changelog: google/error-prone@v2.35.1...v2.36.0
pgjdbc/pgjdbc (org.postgresql:postgresql)
v42.7.5Added
Fixed
fc60537PR #3476Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.