Conversation
renovate-bot
force-pushed
the
renovate/all
branch
7 times, most recently
from
39fbf38 to
6600127
Compare
renovate-bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
27ad2dd to
25dd41e
Compare
renovate-bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
b2dfc73 to
2782588
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
renovate-bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
19dd218 to
08fb697
Compare
lukrus1
approved these changes
Aug 19, 2025
renovate-bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
c9e44f5 to
80f0836
Compare
renovate-bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
b71ff2c to
54fc288
Compare
renovate-bot
force-pushed
the
renovate/all
branch
from
54fc288 to
620da28
Compare
Downgrade dependencyAnalysis version from 2.19.1 to 2.19.0.
kul3r4
pushed a commit
to kul3r4/horologist-1
that referenced
this pull request
Sep 19, 2025
* Update all dependencies --------- Co-authored-by: Yuri Schimke <yuri@schimke.ee>
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
3 participants
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->v58.14.3->9.0.01.74.0->1.75.01.74.0->1.75.01.74.0->1.75.01.12.0->1.15.01.0.0-beta02->1.0.0-beta031.5.0-rc02->1.5.01.5.0-rc02->1.5.01.5.0-rc02->1.5.01.5.0-rc02->1.5.01.5.0-rc02->1.5.01.2.0-beta01->1.2.0-rc011.48.0->1.50.01.48.0->1.50.01.48.0->1.50.01.48.0->1.50.01.48.0->1.50.01.48.0->1.50.01.73.0->1.75.00.8.0->0.9.00.10.7->0.10.84.15.1->4.164.15.1->4.161.73.0->1.75.08.12.0->8.12.22.57->2.57.12.57->2.57.12.57->2.57.12.57->2.57.12.19.0->3.0.11.4.0-beta02->1.4.0-beta034.1->4.1.12.9.2->2.9.32.9.2->2.9.32.9.2->2.9.32.9.2->2.9.32.9.2->2.9.32.9.2->2.9.32.9.2->2.9.32.9.2->2.9.32.9.2->2.9.31.12.0-alpha06->1.12.0-alpha071.12.0-alpha06->1.12.0-alpha071.3.0-beta01->1.3.0-rc011.3.0-beta01->1.3.0-rc011.3.0-beta01->1.3.0-rc01Release Notes
actions/setup-java (actions/setup-java)
v5Compare Source
gradle/gradle (gradle)
v9.0.0Compare Source
grpc/grpc-java (io.grpc:grpc-protobuf-lite)
v1.75.0Behavior Changes
Bug Fixes
core:
grpc-timeoutshould always be positive (#12201) (6dfa03c). There is a local race between when the deadline is checked before sending the RPC and when the timeout is calculated to put on-the-wire. The code replaced negative timeouts with 0 nanoseconds. gRPC’s PROTOCOL-HTTP2 spec states that timeouts should be positive, so now non-positive values are replaced with 1 nanosecondcore: Improved DEADLINE_EXCEEDED message for delayed calls (
6ff8eca). Delayed calls are the first calls on a Channel before name resolution has resolved addresses. Previously you could see confusing errors saying the deadline “will be exceeded in” X time. The message tense was simply wrong, and now will be correct: deadline “was exceeded after” X time.xds: PriorityLB now only uses the failOverTimer to start additional priorities, not fail RPCs (
c4256ad). You should no longer see “Connection timeout for priority” errors.Improvements
netty: Count sent RST_STREAMs against
NettyServerBuilder.maxRstFramesPerWindow()limit (#12288). This extends the Rapid Reset tool to also cover MadeYouReset. the reset stream count will cause a 420 "Enhance your calm response" to be sent. This depends on Netty 4.1.124 for a bug fix to actually call the encoder by the frame writer.xds: Convert CdsLb to
XdsDepManager(297ab05). This is part of gRFC A74 to have atomic xDS config updates. This is an internal change, but does change the error description seen in certain cases, especially DEADLINE_EXCEEDED on a brand-new channel.census: APIs for stats and tracing (#12050) (
9193701). Client channel and server builders with interceptors and factories respectively for stats and tracing.stub: simplify
BlockingClientCallinfinite blocking (#12217) (ba0a732). Move deadline computation into overloads with finite timeouts. Blocking calls without timeouts now do not have to read the clock.xds: Do RLS fallback policy eagar start (#12211) (
42e1829). In gRPC-Java, the xDS clusters were lazily subscribed, which meant the fallback target which is returned in the RLS config wasn’t subscribed until a RPC actually falls back to it. The delayed resource subscription process in gRPC Java made it more susceptible to the effects of the INITIAL_RESOURCE_FETCH_TIMEOUT compared to other programming languages. It also had impact beyond the RLS cache expiration case, for example, when the first time the client initialized the channel, we couldn't fallback when the intended target times out, because of the lazy subscription. This change starts the fallback LB policy for the default target at the start of RLS policy instead of only when falling back to the default target, which fixes the above mentioned problems.xds: Aggregate cluster fixes (A75) (#12186) (
7e982e4). The earlier implementation of aggregate clusters concatenated the priorities from the underlying clusters into a single list, so that it could use a single LB policy defined at the aggregate cluster layer to choose a priority from that combined list. However, it turns out that aggregate clusters don't actually define the LB policy in the aggregate cluster; instead, the aggregate cluster uses a special cluster-provided LB policy that first chooses the underlying cluster and then delegates to the LB policy of the underlying cluster. This change implements that.api: set size correctly for sets and maps in handling
Metadatavalues to be exchanged during a call (#12229) (8021727)xds: xdsClient cache transient error for new watchers (#12291). When a resource update is NACKed, cache the error and update new watchers that get added with that error instead of making them hang.
xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#12289). If a LB policy gives extraneous updates with state CONNECTING, then it was possible to re-create
failOverTimerwhich would then wait the 10 seconds for the child to finish CONNECTING. We only want to give the child one opportunity after transitioning out of READY/IDLE.xds: Use a different log name for
XdsClientImplandControlPlaneClient(#12287).ControlPlaneClientuses "xds-cp-client" now instead of "xds-client" while logging.Dependencies Changes
Upgrade to Netty 4.1.124.Final (#12286). This implicitly disables
NettyAdaptiveCumulator(#11284), which can have a performance impact. We delayed upgrading Netty to give time to rework the optimization, but we've gone too long already without upgrading which causes problems for vulnerability tracking.bazel: Use
jar_jarto avoid xds deps (#12243) (8f09b96). The //xds and //xds:orca targets now usejar_jarto shade the protobuf generated code. This allows them to use their own private copy of the protos and drop direct Bazel dependencies on cel-spec, grpc, rules_go, com_github_cncf_xds, envoy_api, com_envoyproxy_protoc_gen_validate, and opencensus_proto. This mirrors the shading of protobuf messages done for grpc-xds provided on Maven Central and should simplify dependency managementDocumentation
Clarify requirements for creating a cross-user Channel. (#12181). The
@SystemApiruntime visibility requirement isn't really new. It has always been implicit in the required INTERACT_ACROSS_USERS permission, which can only be held by system apps in production. Now deprecatedBinderChannelBuilder#bindAsUserhas always required SDK_INT >= 30. This change just copies that requirement forward to its replacement APIs inAndroidComponentAddressand the TARGET_ANDROID_USERNameResolver.Args.api: Add more Javadoc for
NameResolver.Listener2interface (#12220) (d352540)Thanks to
@benjaminp
@werkt
@kilink
@vimanikag
googleapis/java-genai (com.google.genai:google-genai)
v1.15.0Features
sdkHttpResponse.headersto *Delete responses. (4be038d)Documentation
v1.14.0Features
Bug Fixes
Documentation
v1.13.0Features
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.50.0Compare Source
Fixed: Resolved Gradle task dependency errors with Android Gradle Plugin 8.12+ where
GenerateComposePreviewRobolectricTestsTaskoutput was used by compilation tasks without explicit dependencies. Thank you @papo2608 for reporting this issue.What's Changed
Full Changelog: takahirom/roborazzi@1.49.0...1.50.0
v1.49.0Compare Source
ComposablePreviewScanner 0.7.0 Compatibility Update
Breaking Change - Compatibility Update Required
This release addresses a breaking compatibility issue with ComposablePreviewScanner 0.7.0 that affects users of Roborazzi's Preview support feature.
The Problem
When using ComposablePreviewScanner 0.7.0 with previous versions of Roborazzi, you'll encounter
NoSuchMethodErrorat runtime. This happens because:AndroidPreviewScreenshotIdBuilderto provide commonPreviewScreenshotIdBuildermethods for Glance and Compose MultiplatformThe Solution
This Roborazzi update replaces the old method calls and import statements with new ones compatible with ComposablePreviewScanner 0.7.0+. However, since these new method locations don't exist in ComposablePreviewScanner 0.6.x, you must update both libraries together.
If you use Roborazzi's Preview support, you must:
Both updates are required - updating only one will cause build or runtime errors.
Migration Steps
Improved Error Detection
We've added clear build-time error messages to help you identify when this compatibility issue occurs, so you'll know exactly what needs to be updated instead of encountering cryptic runtime errors.
Common Update Scenarios
Scenario 1: Update only ComposablePreviewScanner to 0.7.0
→
NoSuchMethodErrorwith old Roborazzi. Update Roborazzi to resolve.Scenario 2: Update only Roborazzi
→ Compile-time error with clear message to update ComposablePreviewScanner ✅
Acknowledgments
Thanks to @sergio-sastre for collaboration on resolving this compatibility challenge and maintaining the ComposablePreviewScanner library.
What's Changed
Full Changelog: takahirom/roborazzi@1.48.0...1.49.0
droibit/oss-licenses-android (io.github.droibit.oss-licenses-android:ui-wear-compose-material)
v0.9.0Compare Source
What's Changed
Full Changelog: droibit/oss-licenses-android@0.8.0...0.9.0
Configuration
📅 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.