fix(deps): update java #31
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
dependencies
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
ff5c956 to
350f4ed
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
350f4ed to
8610c5f
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
8610c5f to
c8926ac
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
c8926ac to
f511701
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
f511701 to
0795152
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
0795152 to
c461d32
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
c461d32 to
31f98d0
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
31f98d0 to
e2c6b5c
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
e2c6b5c to
f807360
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
f807360 to
dcb9645
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
dcb9645 to
d1af61f
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
d1af61f to
ea04b67
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
ea04b67 to
a0c17d0
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
9f47c1b to
74d1309
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
74d1309 to
10306f5
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
10306f5 to
65536da
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
65536da to
1c65001
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
1c65001 to
58baa58
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
58baa58 to
03ad0bf
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
03ad0bf to
b83d49e
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
b83d49e to
49e3ada
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
49e3ada to
cd2d7b2
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
cd2d7b2 to
cd3fd3a
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
cd3fd3a to
7162fcb
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
7162fcb to
ba3d6ff
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
ba3d6ff to
02399a7
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
renovate
bot
force-pushed
the
renovate/java
branch
from
02399a7 to
d7c34bb
Compare
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
This PR contains the following updates:
8.10.2->8.12.11.24.0->1.25.22.0.69.Final->2.0.70.Final2.24.1->2.24.32.48.0->2.52.03.25.5->3.25.63.25.5->3.25.62.18.1->2.18.22.18.1->2.18.21.68.1->1.70.01.68.1->1.70.01.68.1->1.70.01.68.1->1.70.01.68.1->1.70.01.68.1->1.70.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
gradle/gradle (gradle)
v8.12.1Compare Source
v8.12Compare Source
v8.11.1: 8.11.1Compare Source
This is a patch release for Gradle 8.11. We recommend users upgrade to 8.11.1 instead of 8.11.
It fixes the following issues:
Read the Release Notes
Upgrade instructions
Switch your build to use Gradle 8.11.1 by updating your wrapper:
See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
v8.11: 8.11Compare Source
The Gradle team is excited to announce Gradle 8.11.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
alyssoncs,
Bilel MEDIMEGH,
Björn Kautler,
Chuck Thomas,
Daniel Lacasse,
Finn Petersen,
JK,
Jérémie Bresson,
luozexuan,
Mahdi Hosseinzadeh,
Markus Gaisbauer,
Matthew Haughton,
Matthew Von-Maszewski,
ploober,
Siarhei,
Titus James,
vrp0211
Upgrade instructions
Switch your build to use Gradle 8.11 by updating your wrapper:
See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
google/google-java-format (googleJavaFormat)
v1.25.2Changes:
Full Changelog: google/google-java-format@v1.25.1...v1.25.2
v1.25.1Changes:
Full Changelog: google/google-java-format@v1.25.0...v1.25.1
v1.25.0The minimum support JDK version to run google-java-format is now JDK 17 (#1159). Using google-java-format to format earlier versions of the language is still supported, but running the formatter itself on JDK 17 or newer is required.
Changes:
whenpattern guardsFull Changelog: google/google-java-format@v1.24.0...v1.25.0
googleapis/sdk-platform-java (com.google.api.grpc:proto-google-common-protos)
v2.52.0Features
Dependencies
9a259c6(#3554) (eb2cbd6)9ab3b6e(#3555) (40a74fe)c7c443f(#3579) (fcf40b7)0a12b5d(#3464) (b9c9d21)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.0Features
java.timeto java-core (#3330) (f202c3b)java.timemethods (#3321) (b21c9a4)Bug Fixes
Dependencies
Documentation
v2.49.0Features
Bug Fixes
Dependencies
protocolbuffers/protobuf (com.google.protobuf:protoc)
v3.25.6grpc/grpc-java (io.grpc:protoc-gen-grpc-java)
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 requestsv1.68.2Bug Fixes
Improvements
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.