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
changed the title
renovate
Bot
changed the title
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
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:
v6→v79.4.1→9.6.14.34.0→4.35.11.1.0→1.1.11.6.0→1.6.11.6.0→1.6.11.6.0→1.6.11.6.0→1.6.11.6.0→1.6.18.7.0→8.8.02.7.0-rc01→2.7.02.7.0-rc01→2.7.02.7.0-rc01→2.7.01.64.0→1.69.01.64.0→1.69.01.64.0→1.69.01.64.0→1.69.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.03.0.0-rc01→3.0.01.0.0-alpha06→1.0.0-alpha071.4.0→1.4.11.4.0→1.4.11.4.0→1.4.11.4.0→1.4.19.0.0→9.1.05.3.1→6.3.08.3.0→8.4.02.3.9→2.3.102.4.0→2.4.102.4.0→2.4.102.4.0→2.4.102.4.0→2.4.102.4.0→2.4.102.4.0→2.4.102.4.0→2.4.102.59.2→2.60.12.59.2→2.60.12.59.2→2.60.11.0.0-beta09→1.0.0-beta101.0.0-alpha12→1.0.0-alpha141.0.0-alpha12→1.0.0-alpha1434.15.0→34.16.017.13.0→17.14.01.0.0-alpha13→1.0.0-alpha151.0.0-alpha13→1.0.0-alpha151.0.0-alpha13→1.0.0-alpha151.11.3→1.11.41.11.3→1.11.41.11.3→1.11.41.11.3→1.11.41.11.3→1.11.41.11.3→1.11.41.11.3→1.11.41.11.3→1.11.41.3.0→1.4.01.1.3→1.1.41.1.3→1.1.41.3.0-alpha01→1.3.0-alpha021.3.0-alpha01→1.3.0-alpha021.3.0-alpha01→1.3.0-alpha021.3.0-alpha01→1.3.0-alpha021.3.0-alpha01→1.3.0-alpha021.3.0-alpha01→1.3.0-alpha021.0.0-alpha02→1.0.0-alpha031.11.3→1.11.42026.06.00→2026.06.019.2.1→9.3.09.2.1→9.3.09.2.1→9.3.09.2.1→9.3.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
actions/checkout (actions/checkout)
v7.0.0Compare Source
v7Compare Source
gradle/gradle (gradle)
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.
v9.5.0: 9.5.0Compare Source
The Gradle team is excited to announce Gradle 9.5.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:
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.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.
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.69.0Compare Source
Performance: faster screenshot capture on the JVM
Every screenshot capture converts an Android
Bitmapinto an AWTBufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixelsetRGBpass plus an extradrawImagecopy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.UI tree dump for AI agents (experimental)
Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:
Each capture then produces three files:
MyTest.uitree.jsonis a grep-first JSON: one node per line carrying all of its attributes, so a singlegrep login_buttonreturns the node's type, bounds, properties, and actions — while staying valid JSON forjq:{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root": { "type": "compose", "bounds": [0, 0, 880, 748], "children": [ { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] } }The annotated image draws each numbered node onto the screenshot — the numbers are exactly the
nvalues in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:
top300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.
Details:
_actualbasename) — including on a failing verify, when you need them most.RoborazziOptions(uiTreeDumpOptions = UiTreeDumpOptions(...)), with a customizable numbering predicate (isAnnotatable) andannotateImage = falseto write only the JSON.Fixes
ImageOutputStreamdoesn't truncate, so trailing bytes of the previous image were left behind and broke webp-imageio's size check on load. Recording now truncates before writing (#886, fixes #881). Thank you @AlexKhomich for the detailed report, and @sergio-sastre for sharing a workaround!What's Changed
Full Changelog: takahirom/roborazzi@1.68.0...1.69.0
v1.68.0Compare Source
Compose Testing v2 (
ui-test-junit4v2) support (experimental)If you've upgraded to Compose 1.11.0, where the v2 testing APIs (
androidx.compose.ui.test.junit4.v2) are the default and the v1 rules are deprecated, Roborazzi now works with the v2 rule factories out of the box —createAndroidComposeRulefrom either package just works withRoborazziRule,captureRoboImage, and generated preview tests.If you have a custom
ComposePreviewTester, you can also delete the unchecked cast that used to be required:What you might need to change
Most users need no changes. The exception: the options APIs now accept the
ComposeTestRule/ComposeContentTestRuleinterfaces instead of the concreteAndroidComposeTestRule<...>type, socomposeTestRule.activityRuleis no longer reachable through them. Roborazzi finds your rule's activity automatically; if it can't, it fails loudly (instead of silently capturing the wrong activity) and tells you to pass the scenario yourself:composeTestRule(rule) { activityScenario }for direct capture callsJUnit4TestLifecycleOptions.activityScenarioProviderfor generated preview testsThe new
sample-compose-v2module shows both, running against stable Compose 1.11.0.Compatibility
Libraries compiled against 1.67.0 keep working — the old entry points are preserved as hidden binary-compat bridges. If you compile against 1.68.0, typical code compiles as-is (or gets simpler, as above). Known remaining binary-level changes on these
@ExperimentalRoborazziApisurfaces:JUnit4TestParameter.getComposeTestRule's return type and the data-classcopysignatures ofJUnit4TestLifecycleOptions/RoborazziComposeTestRuleOption; recompiling resolves them.@PreviewWrapperpreviews now appear correctly in screenshotsIf you use Compose UI 1.11's
@PreviewWrapperto wrap previews in a theme or background, those wrappers now show up in your Roborazzi preview screenshots with no extra setup — just use ComposablePreviewScanner 0.9.0 or later (#823):This is verified by a sample preview test, and the docs have a new PreviewWrapper support section. Huge thanks to @sergio-sastre for implementing the automatic wrapping in ComposablePreviewScanner 0.9.0!
What's Changed
**Fu
Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.