Open
Conversation
renovate-bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
f14e4db to
1cdc217
Compare
renovate-bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
77923cd to
17c6741
Compare
renovate-bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
24ff9ae to
4ce96ce
Compare
renovate-bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
ad5d35b to
67588dd
Compare
renovate-bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
014cb84 to
e8b071d
Compare
renovate-bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
eef97fd to
f9e8201
Compare
renovate-bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
298b22f to
970a275
Compare
renovate-bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
8924f95 to
3e04e3f
Compare
renovate-bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
c7733a2 to
f95e409
Compare
renovate-bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
c6f4a2e to
5b57b8d
Compare
renovate-bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
2025390 to
ac2a2b2
Compare
renovate-bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
fac801f to
4144ef2
Compare
renovate-bot
force-pushed
the
renovate/all
branch
from
4144ef2 to
618a144
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
v4→v5v5→v6v5→v6v4→v78.14.3→9.4.0v6→v70.9.5→0.9.618.9.0→18.10.01.73.0→1.79.01.4.3→1.5.01.73.0→1.79.01.73.0→1.79.01.30.0→1.43.03.3.6→3.4.28.12.3→9.1.01.6.0-alpha06→1.6.0-rc011.6.0-alpha06→1.6.0-rc011.6.0-alpha06→1.6.0-rc011.6.0-alpha06→1.6.0-rc011.6.0-alpha06→1.6.0-rc017.2.1→8.3.01.10.0→1.10.51.52.0→1.59.01.52.0→1.59.01.52.0→1.59.01.52.0→1.59.01.52.0→1.59.01.52.0→1.59.01.73.0→1.79.017.3.0→17.4.021.4.0→21.5.10.9.0→0.10.00.10.9→0.10.104.16→4.16.14.16→4.16.13.16.4→3.17.00.4.0-alpha03→0.5.01.73.0→1.79.00.34.0→0.36.00.34.0→0.36.02.57.2→2.59.22.57.2→2.59.22.57.2→2.59.22.57.2→2.59.22.0.0→2.1.02.0.0→2.1.02.19.0→3.6.12.11.0→2.11.12.11.0→2.11.11.4.0-alpha02→1.4.01.1.0→1.2.04.1.1→4.3.22.9.6→2.9.72.9.6→2.9.72.9.6→2.9.71.17.0→1.18.01.17.0→1.18.01.12.1→1.13.01.12.1→1.13.01.3.0-alpha07→1.3.01.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.8.0→1.9.21.1.0-alpha05→1.1.0-rc011.3.0-alpha07→1.3.0Release Notes
actions/cache (actions/cache)
v5Compare Source
actions/checkout (actions/checkout)
v6Compare Source
actions/setup-python (actions/setup-python)
v6Compare Source
actions/upload-artifact (actions/upload-artifact)
v7Compare Source
v6Compare Source
v5Compare Source
gradle/gradle (gradle)
v9.4.0Compare Source
v9.3.1: 9.3.1Compare Source
This is a patch release for 9.3.0. We recommend using 9.3.1 instead of 9.3.0.
The following issues were resolved:
Read the Release Notes
Upgrade instructions
Switch your build to use Gradle 9.3.1 by updating your wrapper:
See the Gradle 9.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.
v9.3.0Compare Source
v9.2.1: 9.2.1Compare Source
The Gradle team is excited to announce Gradle 9.2.1.
Here are the highlights of this release:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
Björn Kautler,
hasunzo,
HYEON,
Hyunjoon Park,
HYUNJUN SON,
Jendrik Johannes,
Kirill Gavrilov,
Madalin Valceleanu,
Martin Bonnin,
Matthew Haughton,
Mikhail Polivakha,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Róbert Papp,
Simon Marquis,
TheGoesen,
Vincent Potucek,
Xin Wang.
Upgrade instructions
Switch your build to use Gradle 9.2.1 by updating your wrapper:
See the Gradle 9.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.
v9.2.0Compare Source
v9.1.0: 9.1.0Compare Source
The Gradle team is excited to announce Gradle 9.1.0.
Here are the highlights of this release:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Eng Zer Jun,
EunHyunsu,
Gaëtan Muller,
HeeChul Yang,
Jendrik Johannes,
Johnny Lim,
Junho Lee,
Kirill Gavrilov,
Matthew Haughton,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Pradyumna C,
r-a-sattarov,
Ryszard Perkowski,
Sebastian Schuberth,
SebastianHeil,
Staffan Al-Kadhimi,
winfriedgerlach,
Xin Wang.
Upgrade instructions
Switch your build to use Gradle 9.1.0 by updating your wrapper:
See the Gradle 9.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.
v9.0.0: 9.0.0Compare Source
The Gradle team is excited to announce Gradle 9.0.0.
Here are the highlights of this release:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Aaron Matthis,
Adam E,
Adam S,
Björn Kautler,
Daniel Lacasse,
Eng Zer Jun,
EunHyunsu,
FlorianMichael,
Francisco Prieto,
Gaëtan Muller,
Jake Wharton,
Kengo TODA,
Kent Kaseda,
Madalin Valceleanu,
Marc Philipp,
Mark S. Lewis,
Matthew Haughton,
Mycroft Wong,
Na Minhyeok,
Nelson Osacky,
Olivier "Oli" Dagenais,
ploober,
Radai Rosenblatt,
Róbert Papp,
Sebastian Schuberth,
Victor Merkulov.
Upgrade instructions
Switch your build to use Gradle 9.0.0 by updating your wrapper:
See the Gradle 9.0.0 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.14.4Compare Source
stefanzweifel/git-auto-commit-action (stefanzweifel/git-auto-commit-action)
v7Compare Source
Added
Changes
Dependency Updates
grpc/grpc-java (io.grpc:grpc-protobuf-lite)
v1.79.0API Changes
core: Delete the never-used io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (#12580) (
738782f). This is deeply internal and not accessible, so shouldn’t impact anything. However, Apache Arrow Java uses reflection to access private fields; GH-939: Remove reflection for gRPC buffers is swapping to gRPC’s public zero-copy APIsopentelemetry: Add target attribute filter for metrics (#12587). Introduce an optional Predicate targetAttributeFilter to control how grpc.target is recorded in OpenTelemetry client metrics. When a filter is provided, targets rejected by the predicate are normalized to "other" to reduce grpc.target metric cardinality, while accepted targets are recorded as-is. If no filter is set, existing behavior is preserved. This change adds a new Builder API on GrpcOpenTelemetry to allow applications to configure the filter.
Behavior Changes
core: Convert AutoConfiguredLB to an actual LB (
4bbf8ee). This is an internal refactoring, but it does improve how errors are handled for broken binaries. Previously, not being able to load pick_first would result in a channel panic. Now it is handled as a regular load balancing errorokhttp: Assert no pending streams before transport READY (#12566) (
ed6d175). No pending streams should exist when the transport transitions to READY. This PR adds an assertion to help verify this invariant.Bug Fixes
228fc8e). Pick-first in grpc-java has behaved this way since it was created, and it was of no consequence. However, now there are some load balancing policies (mainly RLS) that will do a pick() and hope the result to be reasonably accurate for metrics.Improvements
core: Improve DEADLINE_EXCEEDED message for CallCreds delays (
ead532b). Previously the error message contained “buffered_nanos” and “waiting_for_connection” for connection delays. However, we discovered the same strings were also used if waiting on CallCredentials. Now you’ll see details like “connecting_and_lb_delay”, “call_credentials_delay”, and “was_still_waiting”.opentelemetry: Add Android API checking (
a9f73f4). Previously we assumed OpenTelemetry support would not be used on Android. It did happen to be compatible with Android, but since OpenTelemetry does have some Android support, we now have a check that it remains compatiblecore: Catch Errors when calling complex config parsing code (
a535ed7). Error (and any other Throwable) is now caught and handled when parsing configuration (e.g., service config, xds). This will cause such failures to be handled gracefully instead of panicking the channelcore: Implement LoadBalancer.Helper.createOobChannel() with the internals of createResolvingOobChannel() (
3915d02). This API is only expected to be relevant to the gRPC-LB lookaside load balancer, and is not believed to have behavior changes. Out-of-band channel had been implemented with its own stripped-down Channel without load balancing. Reimplementing using the resolving oob channel makes it a full-fledged channel and reduces the burden when integrating new features and allows us to have a ManagedChannelBuilder to use with efforts like gRFC A110: Child Channel Options.xds: Implement the proactive connection logic in RingHashLoadBalancer as outlined in gRFC A61 (#12596). Previously, the Java implementation only initialized child balancers when a ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel call. This PR adds the missing logic: when a child balancer reports TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first available IDLE child if no other children are currently connecting or ready.
This ensures a backup subchannel starts warming up immediately outside the RPC flow, reducing failover latency and improving overall resilience. This behavior was previously present but was inadvertently lost after #10610.
f65127c) Experimental RFC 3986 target URI parsing mode (disabled by default)New Features
6b2f758), completing the remaining work in gRFC A96: OTel metrics for SubchannelsDependencies
protobuf: Upgrade Bazel protobuf to 33.1 (#12553) (
b61a8f4) and load java_proto_library from the protobuf repo (c7f3cdb)protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and grpc-proto versions (#12569)
Upgrade dependencies (#12588) (
6422092) Netty to 4.1.130, error-prone annotations to 2.45.0, google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 1.41.0, proto-google-common-protos to 2.63.2.Thanks to
v1.78.0Bug Fixes
02e98a8). This fixes a race where RPCs could fail with "UNAVAILABLE: Channel shutdown invoked" even though they were created before channel.shutdown()8d49dc1)thisfrom BinderServerTransport's ctor (#12453) (89d77e0)55ae1d0). This fixes a regression since 1.75.0 triggered by CdsLb being converted to XdsDepManager. Without this fix, a second channel to the same target may hang when starting, causing DEADLINE_EXCEEDED, and unhang when the control plane delivers an update (e.g., endpoint address update)Improvements
f385add). We now have improved xDS error handling and this provides a clearer mechanism for the xDS server to report per-resource errors to the client, resulting in better error messages for debugging and faster detection of non-existent resources. This also improves the handling of all xDS-related data errors and the behavior of the xDS resource timer.26c1c13). Resets RLS request backoff timers when the Control plane channel state transitions to READY. Also when the backoff timer expires, instead of making a RLS request immediately, it just causes a picker update to allow making rpc again to the RLS target.4843256)283f103)bbc0aa3)9313e87)725ab22)cb73f21). Shared resources are internal to gRPC for sharing expensive objects across channels and servers, like threads. This reduces the chances of forming a deadlock, like seen with s2a ind50098f6dab2ce)f36defa). proto-google-common-protos to 2.63.1, google-auth-library to 1.40.0, error-prone annotations to 2.44.0, guava to 33.5.0-android, opentelemetry to 1.56.02f64092)d971072). Adds support forandroid:isolatedProcessServices and moves all security checks to the handshake, making subsequent transactions more efficient.New Features
58ae5f8).48a4288). The policy uses the namerandom_subsetting_experimental. If it is working for you, tell us so we can gauge marking it stable. While the xDS portions haven’t yet landed, it is possible to use with xDS with JSON-style Structs as supported by gRFC A5251611ba). Most service mesh workloads use mTLS, as described in gRFC A29. However, there are cases where it is useful for applications to use normal TLS rather than using certificates for workload identity, such as when a mesh wants to move some workloads behind a reverse proxy. The xDSCertificateValidationContextmessage (see envoyproxy/envoy#34235) has asystem_root_certsfield. In the gRPC client, if this field is present and theca_certificate_provider_instancefield is unset, system root certificates will be used for validation. This implements [gRFC AConfiguration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (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.