Update Samples dependencies #204
Open
+60
−50
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/samples
branch
from
8d8cae9 to
ae3910d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/samples
branch
9 times, most recently
from
217d48d to
7a42915
Compare
renovate
bot
force-pushed
the
renovate/samples
branch
8 times, most recently
from
61acd80 to
0e59d54
Compare
renovate
bot
force-pushed
the
renovate/samples
branch
3 times, most recently
from
3f635c1 to
671c4bc
Compare
renovate
bot
force-pushed
the
renovate/samples
branch
6 times, most recently
from
4bf83a5 to
a6e90c7
Compare
renovate
bot
force-pushed
the
renovate/samples
branch
7 times, most recently
from
094b0ae to
5990a21
Compare
renovate
bot
force-pushed
the
renovate/samples
branch
9 times, most recently
from
f9b9d8b to
1f958f3
Compare
renovate
bot
force-pushed
the
renovate/samples
branch
12 times, most recently
from
81f73a5 to
17657b0
Compare
renovate
bot
force-pushed
the
renovate/samples
branch
from
17657b0 to
7d851d9
Compare
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:
8.12->8.131.5.16->1.5.180.5.1->0.6.00.5.1->0.6.00.5.1->0.6.00.5.1->0.6.00.5.1->0.6.01.69.0->1.71.00.5.1-grpc-16->0.5.1-grpc-390.5.1->0.6.00.5.1->0.6.01.8.0->1.8.11.8.0->1.8.13.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.23.0.3->3.1.21.8.0-alpha01->1.8.0-SNAPSHOT+pull-52451.7.6->1.7.81.7.6->1.7.80.9.4->0.9.50.5.1-grpc-16->0.6.02.2.0->2.2.11.7.6->1.7.81.7.6->1.7.81.7.6->1.7.81.7.6->1.7.81.7.6->1.7.81.9.3->1.10.12025.1.2->2025.4.58.8.0-alpha05->8.9.18.8.0-alpha05->8.9.18.8.0->8.9.1Release Notes
gradle/gradle (gradle)
v8.13Compare Source
v8.12.1: 8.12.1Compare Source
The Gradle team is excited to announce Gradle 8.12.1.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Abhiraj Adhikary,
Ayush Saxena,
Björn Kautler,
davidburstrom,
Dominic Fellbaum,
Emmanuel Ferdman,
Finn Petersen,
Johnny Lim,
Mahdi Hosseinzadeh,
Martin Bonnin,
Paint_Ninja,
Petter Måhlén,
Philip Wedemann,
stegeto22,
Tanish,
TheGoesen,
Tim Nielens,
Trout Zhang,
Victor Merkulov
Upgrade instructions
Switch your build to use Gradle 8.12.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.
Kotlin/kotlinx-rpc (org.jetbrains.kotlinx:kotlinx-rpc-krpc-ktor-server)
v0.6.0Compare Source
Features 🎉
Documentation 📗
Infra 🚧
Other Changes 🧹
Full Changelog: 0.5.1...0.6.0
grpc/grpc-java (io.grpc:grpc-netty)
v1.71.0API Changes
176f3ee)ProtoUtilsis now stabilized (#11884) (90b1c4f)Bug Fixes
199a7ea). They were previously processed as int32, although the sum of weights was checked to be positive. So this would have caused a very large weight to never be selected and to reduce the chances of immediately-following clusters to be selected. There have been no reports of control planes using such large weights199a7ea). Triggering required the old cluster to no longer be used, an RPC processing when the update arrived, and for a RPC to not match any route in the new config. There have been no reports of this actually happeningdc316f7)Improvements
CheckReturnValuewith Error Prone's (#11811) (7b5d069)5a7f350)44e92e2)7585b16). This makes it much easier to debug connectivity issues when using wait-for-ready RPCs0f5503e)MessageFramer.flush() is being called between every message, so messages are never combined and the larger allocation just wastes memory. (4a10a38,7153ff8)ClientStreamObservercloses the response observer log the error message if this operation fails (#11880) (302342c)3142928)c506190,b3db8c2). This was an internal refactor that should have no user-visible changeAltsContextUtilto allow getting theAltsContexton client-side (b1bc0a9)b44ebce)Documentation
HelloWorldServerto use Executor (#11850) (16edf7a)9e86299)Dependencies
fc8571a)122b683)Thanks to
@benjamin
@panchenko
@harshagoo94
@NaveenPrasannaV
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. TrConfiguration
📅 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.