Update all dependencies - #840
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
March 18, 2026 21:58
6d63750 to
e0cffe1
Compare
dturner
approved these changes
Mar 19, 2026
renovate
Bot
force-pushed
the
renovate/all
branch
11 times, most recently
from
March 25, 2026 22:26
3642b22 to
58cf231
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
April 2, 2026 07:14
3129112 to
e078b5d
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
April 7, 2026 13:30
b626af9 to
d4a6f2e
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
15 times, most recently
from
April 24, 2026 17:34
7628abc to
1d66b16
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
11 times, most recently
from
May 5, 2026 01:56
083fdfb to
0f41ddd
Compare
pflammertsma
requested changes
Jun 18, 2026
Member
There was a problem hiding this comment.
We need to bump this to 37.
Contributor
|
@android/devrel-xr There's an issue with the XR unit tests, can you look into it? |
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
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:
v6→v7v5→v69.5.0→9.7.11.16.0→1.17.04.34.0→4.36.01.3.0→2.0.18.9.0→8.10.13.0.1→3.0.23.0.1→3.0.23.0.1→3.0.23.0.1→3.0.23.0.1→3.0.23.0.1→3.0.23.0.1→3.0.23.0.1→3.0.23.0.1→3.0.23.0.1→3.0.21.70.0→1.73.01.70.0→1.73.01.70.0→1.73.01.70.0→1.73.01.0.0-alpha09→1.0.0-alpha104.35.1→4.36.05.4.0→5.5.05.3.1→6.3.01.10.1→1.11.01.10.1→1.11.01.10.1→1.11.01.10.1→1.11.01.10.1→1.11.01.10.1→1.11.01.10.1→1.11.08.4.0→8.5.02.3.10→2.3.111.2.0-alpha04→1.2.0-alpha0633.6.0-jre→33.7.1-jre0.59.0→0.61.01.54.0→1.56.01.0.0-alpha14→1.0.0-alpha171.0.0-alpha14→1.0.0-alpha171.0.0-alpha14→1.0.0-alpha1716.0.0-beta03→16.0.0-beta0534.17.0→34.18.017.15.0→17.16.01.0.0-alpha17→1.0.0-alpha181.0.0-alpha17→1.0.0-alpha181.0.0-alpha17→1.0.0-alpha181.6.1→1.6.23.5.0→3.5.13.5.0→3.5.11.1.5→1.1.71.1.5→1.1.72.9.8→2.10.01.8.9→1.9.01.8.9→1.9.01.0.0-alpha02→1.0.0-alpha041.1.0-alpha06→1.1.0-beta011.0.0-alpha10→1.0.0-alpha111.0.0-alpha10→1.0.0-alpha111.6.1→1.6.21.6.1→1.6.21.6.1→1.6.21.6.1→1.6.21.6.1→1.6.21.6.1→1.6.21.6.1→1.6.21.6.1→1.6.21.0.0-alpha10→1.0.0-alpha111.0.0-alpha10→1.0.0-alpha111.7.1→1.8.09.3.1→9.3.29.3.1→9.3.29.3.1→9.3.29.3.1→9.3.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/checkout (actions/checkout)
v7.0.1Compare Source
v7.0.0Compare Source
actions/setup-java (actions/setup-java)
v6.0.0Compare Source
gradle/gradle (gradle)
v9.7.1Compare Source
v9.7.0Compare Source
v9.6.1Compare Source
v9.6.0Compare Source
v9.5.1: 9.5.1Compare Source
The Gradle team is excited to announce Gradle 9.5.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:
atm1020,
mataha,
Adam,
Attila Kelemen,
Benedikt Ritter,
Björn Kautler,
Caro Silva Rode,
CHANHAN,
Dmitry Nezavitin,
Eng Zer Jun,
KugelLibelle,
Madalin Valceleanu,
Markus Gaisbauer,
Oliver Kopp,
Philip Wedemann,
ploober,
Roberto Perez Alcolea,
Rohit Anand,
Suvrat Acharya,
Ujwal Suresh Vanjare,
Victor Merkulov
Upgrade instructions
Switch your build to use Gradle 9.5.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.
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.73.0Compare Source
Performance
ImageComparatoronly when they differ. Results are unchanged. An identical 1080x2340 comparison drops from 15.3ms to 0.37ms (#917). Thank you @AlexanderGH for the optimization and the thorough tests!Fixes
generateComposePreviewRobolectricTests. The generated tests were registered as an unnamed, absolute-path input, so cache entries were never reused across checkouts (e.g. CI → local). The input is now relative-path normalized; a second checkout at a different path resolves FROM-CACHE (#919, fixes #918). Thank you @technoir42 for the precise report and suggested fix!What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.72.0...1.73.0
v1.72.0Compare Source
New: Subdirectory naming strategies for screenshot paths
Two new
roborazzi.record.namingStrategyoptions organize screenshots into directories instead of one flat folder of fully-qualified file names (#909, fixes #801):Why: with
generateComposePreviewRobolectricTests, projects with hundreds of previews end up with a single flat directory that is hard to navigate. Both directory styles requested in the issue discussion are supported._compare/_actualimages mirror the golden's subdirectory. This matters because the package no longer appears in the leaf file name with the*Dirstrategies — without mirroring, two classes with the same simple name in different packages would collapse onto a single flat comparison image. The mirroring also works when the compare output directory is a separate directory, and when the output directory is overridden viaRoborazziRule. The three existing strategies produce byte-for-byte identical paths as before, so nothing changes unless you opt in.Fixes
roborazzi.record.filePathStrategy=relativePathFromRoborazziContextOutputDirectory, the output directory was prepended twice on Windows (D:\...\screenshots\D:\...\screenshots\Test.png), because the absolute-path guard only recognized Unix-style paths —D:\...fell through and was joined to the output directory again. Windows drive-absolute and UNC paths are now detected as absolute; on Unix,:and\remain valid file name characters, so nothing changes there (#916, fixes #915). Thank you @MGaetan89 for the report with a minimal reproducer while re-enabling the Roborazzi integration tests on Robolectric!What's Changed
Full Changelog: takahirom/roborazzi@1.71.0...1.72.0
v1.71.0Compare Source
🎉 1,000 stars
Roborazzi just passed 1,000 stars. Thank you to everyone who has filed an issue, sent a PR, shared a workaround, or just tried it on a project and told us what broke — this release is two bug reports and their fixes, which is a pretty good picture of how the library actually gets better.
Fixes
Both fixes are in the UI tree dump shipped in 1.69.0.
captureRoboImage { content() }. The sidecar held only the root view shell, with no Compose semantics nodes at all — on every composable, and on the Compose Preview scanner path too, which delegates to the same overload.RoboComponent.defaultChildVisitoronly descended into semantics for anAbstractComposeView, but this path passes theAndroidComposeViewas the capture root: not anAbstractComposeView, just aViewGroupthat itself implementsViewRootForTest. Traversal fell through to the plainViewGroupbranch and stopped. It now descends for aViewRootForTestas well, which also restores the Compose boxes incaptureType = Dumpimages on this path (#914, fixes #913). Thank you @danielkatfavor for the clear report with the exact sidecar output!CustomActionsserialization was non-deterministic. ACustomAccessibilityAction's action lambda is serialized viatoString(), which carries JVM runtime identity, so the value changed on every run and re-recording produced golden churn with no UI change behind it. Custom actions now serialize asCustomAccessibilityAction(label=...), and collection values are serialized element-wise before sorting so ordering is stable too (#911, fixes #910). Thank you @hellohj for reporting this!What's Changed
Full Changelog: takahirom/roborazzi@1.70.0...1.71.0
lysine-dev/okhttp (com.squareup.okhttp3:okhttp)
v5.5.02026-08-16
This release introduces opt-in support for [Encrypted Client Hello (ECH)]. This new feature
improves user privacy by encrypting domain names in transit. With regular TLS, your coffee shop’s
Wi-Fi router can see that you’re visiting wikipedia.com, but it cannot see which page you’re
looking at. With ECH, the router observes only the IP address. This additional privacy is most
effective on sites hosted by big CDNs because the IP address doesn’t imply a particular website.
This requires ECH support in the platform’s TLS stack. Today this is only Android 17 (API 37,
released June 2026). When other TLS stacks add ECH support, we'll integrate them.
ECH took a lot of work to implement because the encryption keys are published over DNS in the
[HTTPS resource record], and we needed to write new code to fetch these records. This release
includes a major update to OkHttp’s DNS API: it now supports multiple resource record types (not
just IP addresses!), asynchronous streaming results, and in-memory caching.
To opt in, you can use
DnsOverHttps:You could also opt in with our new
AndroidDnsAPI. Unfortunately, the privacy benefits of ECH aredeficient because its DNS queries are not encrypted by default.
projects ([Retrofit], [Okio], and [SQLDelight]) recently joined [the Commonhaus Foundation].
@StartStopannotation now supports@NestedJUnit 5 tests.weren’t applied correctly.
the HTTP call to crash.
mockito/mockito-kotlin (org.mockito.kotlin:mockito-kotlin)
v6.3.0Changelog generated by Shipkit Changelog Gradle Plugin
6.3.0
v6.2.3Changelog generated by Shipkit Changelog Gradle Plugin
6.2.3
v6.2.2Changelog generated by Shipkit Changelog Gradle Plugin
6.2.2
v6.2.1Changelog generated by Shipkit Changelog Gradle Plugin
6.2.1
v6.2.0Changelog generated by Shipkit Changelog Gradle Plugin
6.2.0
Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 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.