Skip to content

Update all dependencies#53

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all
Open

Update all dependencies#53
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Mar 24, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
actions/checkout action major v6v7 age confidence
gradle (source) minor 9.4.19.6.1 age confidence
gradle/actions action major v5v6 age confidence
io.github.takahirom.roborazzi plugin minor 1.59.01.70.0 age confidence
io.github.takahirom.roborazzi:roborazzi-junit-rule dependencies minor 1.59.01.70.0 age confidence
io.github.takahirom.roborazzi:roborazzi-compose dependencies minor 1.59.01.70.0 age confidence
io.github.takahirom.roborazzi:roborazzi dependencies minor 1.59.01.70.0 age confidence
org.jetbrains.kotlinx:kotlinx-coroutines-test dependencies minor 1.10.21.11.0 age confidence
org.mockito.kotlin:mockito-kotlin dependencies minor 6.2.36.3.0 age confidence
org.jetbrains.kotlin.plugin.compose (source) plugin minor 2.3.202.4.10 age confidence
com.google.devtools.ksp (source) plugin patch 2.3.62.3.10 age confidence
com.google.protobuf:protobuf-javalite (source) dependencies minor 4.34.04.35.1 age confidence
androidx.navigation:navigation-compose (source) dependencies patch 2.9.72.9.8 age confidence
androidx.navigation:navigation-runtime-ktx (source) dependencies patch 2.9.72.9.8 age confidence
androidx.lifecycle:lifecycle-runtime-compose (source) dependencies minor 2.10.02.11.0 age confidence
androidx.lifecycle:lifecycle-viewmodel-compose (source) dependencies minor 2.10.02.11.0 age confidence
androidx.compose:compose-bom dependencies minor 2026.03.002026.06.01 age confidence
com.google.dagger.hilt.android plugin minor 2.59.22.60.1 age confidence
androidx.lifecycle:lifecycle-runtime-ktx (source) dependencies minor 2.10.02.11.0 age confidence
com.google.protobuf:protoc (source) dependencies minor 4.34.04.35.1 age confidence
org.jetbrains.kotlinx:kotlinx-serialization-json dependencies minor 1.10.01.11.0 age confidence
org.jetbrains.kotlin.plugin.serialization (source) plugin minor 2.3.202.4.10 age confidence
androidx.core:core-ktx (source) dependencies minor 1.18.01.19.0 age confidence
org.jetbrains.kotlin.android (source) plugin minor 2.3.202.4.10 age confidence
androidx.hilt:hilt-navigation-compose (source) dependencies minor 1.3.01.4.0 age confidence
com.google.dagger:hilt-android-testing dependencies minor 2.59.22.60.1 age confidence
com.google.dagger:hilt-android-compiler dependencies minor 2.59.22.60.1 age confidence
com.google.dagger:hilt-android dependencies minor 2.59.22.60.1 age confidence
androidx.compose.foundation:foundation (source) dependencies minor 1.10.51.11.4 age confidence
com.google.protobuf plugin minor 0.9.60.10.0 age confidence
io.coil-kt.coil3:coil-network-okhttp dependencies minor 3.4.03.5.0 age confidence
io.coil-kt.coil3:coil-compose dependencies minor 3.4.03.5.0 age confidence
com.android.library (source) plugin minor 9.1.09.3.0 age confidence
com.android.application (source) plugin minor 9.1.09.3.0 age confidence

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

v7

Compare Source

gradle/gradle (gradle)

v9.6.1

Compare Source

v9.6.0

Compare Source

v9.5.1: 9.5.1

Compare Source

The Gradle team is excited to announce Gradle 9.5.1.

Here are the highlights of this release:

  • Task provenance in reports and failure messages
  • Type-safe accessors for precompiled Kotlin Settings plugins

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:

./gradlew wrapper --gradle-version=9.5.1 && ./gradlew 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.0

Compare Source

The Gradle team is excited to announce Gradle 9.5.0.

Here are the highlights of this release:

  • Task provenance in reports and failure messages
  • Type-safe accessors for precompiled Kotlin Settings plugins

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:

./gradlew wrapper --gradle-version=9.5.0 && ./gradlew 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.

gradle/actions (gradle/actions)

v6.2.0

Compare Source

Highlights

This release brings significant behaviour improvements to Enhanced caching, improvements to the generated Job Summary, and a number of correctness and security fixes.

  1. Improved cache-cleanup mechanism. Cleanup of stale files from the Gradle User Home is now faster, and no longer depends on Gradle or a JVM. It works by inspecting the local file state directly, removing the Gradle invocation from the post-build step.
  2. More granular, more stable caching. The local build cache is stored as a separate cache entry, so it can be restored and invalidated independently of the main Gradle User Home entry. Transient Gradle housekeeping files are excluded from the cache, reducing its size and improving stability.
  3. Hide obsolete Job summaries in PR commments: When a new Job summary comment is added to a PR, previous outdated Job summaries are now hidden.
  4. Improved caching report in the job summary. The cache report now uses a single, consistent layout across all cache states and providers. Provider information is integrated directly into the report, and per-entry details are available in an expandable section. (#​985)
  5. Correctness and security fixes. A unique cache key is now used per run attempt, so re-runs no longer collide; the job summary shows the cache key string rather than an internal id; and bundled dependencies have been updated, including a ReDoS fix and a fast-xml CVE fix.
What's Changed
New Contributors

Full Changelog: gradle/actions@v6.1.1...v6.2.0

v6.1.1

Compare Source

This release updates various dependency versions, resolving several reported security vulnerabilities.
No functional changes are included

What's Changed

Full Changelog: gradle/actions@v6.1.0...v6.1.1

v6.1.0

Compare Source

New: Basic Cache Provider

A new MIT-licensed Basic Caching provider is now available as an alternative to the proprietary Enhanced Caching provided by gradle-actions-caching. Choose Basic Caching by setting cache-provider: basic on setup-gradle or dependency-submission actions.

  • Built on @actions/cache -- fully open source
  • Caches ~/.gradle/caches and ~/.gradle/wrapper directories
  • Cache key derived from build files (*.gradle*, gradle-wrapper.properties, etc.)
  • Clean cache on build file changes (no restore keys, preventing stale entry accumulation)

Limitations vs Enhanced Caching: No cache cleanup, no deduplication of cached content, cached content is fixed unless build files change.

Revamped Licensing & Distribution Documentation
  • New DISTRIBUTION.md documents the licensing of each component (particularly Basic Caching vs Enhanced Caching)
  • Simplified licensing notices in README, docs, and runtime log output
  • Clear usage tiers: Enhanced Caching is free for public repos and in Free Preview for private repos
What's Changed

Full Changelog: gradle/actions@v6.0.1...v6.1.0

v6.0.1

Compare Source

[!IMPORTANT]
The release of gradle/actions@v6 contains important changes to the license terms. More details in this blog post.
TL;DR: By upgrading to v6, you accept the Terms of Use for the gradle-actions-caching component.

Summary

The license changes in v6 introduced a gradle-actions-caching license notice that is printed in logs and in each job summary.

With this release, the license notice will be muted if build-scan terms have been accepted, or if a Develocity access key is provided.

What's Changed
  • Bump actions used in docs by @​Goooler in #​792
  • Add typing information for use by typesafegithub by @​bigdaz in #​910
  • Mute license warning when terms are accepted by @​bigdaz in #​911
  • Mention explicit license acceptance in notice by @​bigdaz in #​912
  • Bump com.fasterxml.jackson.dataformat:jackson-dataformat-smile from 2.21.1 to 2.21.2 in /sources/test/init-scripts in the gradle group across 1 directory by @​dependabot[bot] in #​907

Full Changelog: gradle/actions@v6.0.0...v6.0.1

v6.0.0

Compare Source

[!IMPORTANT]
The release of gradle/actions@v6 contains important changes to the license terms. More details in this blog post.
TL;DR: By upgrading to v6, you accept the Terms of Use for the gradle-actions-caching component.

Summary
  • Caching functionality of 'gradle-actions' has been extracted into a separate gradle-actions-caching library, and is no longer open-source. See this blog post for more context.
  • Existing, rudimentary, configuration-cache support has been removed, pending a fully functional implementation in gradle-actions-caching.
  • Dependencies updated to address security vulnerabilities

[!IMPORTANT]

Licensing notice

The caching functionality in `gradle-actions` has been extracted into `gradle-actions-caching`, a proprietary commercial component that is not covered by the MIT License.
The bundled `gradle-actions-caching` component is licensed and governed by a separate license, available at https://gradle.com/legal/terms-of-use/.

The `gradle-actions-caching` component is used only when caching is enabled and is not loaded or used when caching is disabled.

Use of the `gradle-actions-caching` component is subject to a separate license, available at https://gradle.com/legal/terms-of-use/.
If you do not agree to these license terms, do not use the `gradle-actions-caching` component.

What's Changed

Full Changelog: gradle/actions@v5.0.2...v6.0.0

v6

Compare Source

takahirom/roborazzi (io.github.takahirom.roborazzi)

v1.70.0

Compare Source

Experimental: Compose Preview screenshot tests for Compose Desktop

[!NOTE]
Desktop preview support is experimental — feedback welcome in the issues.

Roborazzi can now generate preview screenshot tests for the Compose Desktop (JVM) target — no Robolectric involved (#​897, #​898, #​899). Previews are scanned with ComposablePreviewScanner's android artifact, which is a pure-JVM jar, so multiplatform @Previews declared in commonMain are found on the desktop classpath too:

roborazzi {
  @​OptIn(ExperimentalRoborazziApi::class)
  generateComposePreviewDesktopTests {
    enable = true
    packages = listOf("com.example")
  }
}
./gradlew recordRoborazziDesktop   # compareRoborazziDesktop / verifyRoborazziDesktop

Why: Desktop-only Compose apps had no preview screenshot testing at all. Multiplatform projects could already capture their common previews with the Robolectric preview tests — the desktop tests are an alternative that runs roughly 4–6x faster (benchmark) by skipping the Android unit test environment (Robolectric) entirely. Robolectric remains the right choice when Android rendering fidelity matters: the two produce different images, so goldens are per-platform.

Feature parity with the Robolectric preview tests (#​900, #​902, #​904): @Preview annotation options (widthDp/heightDp, fontScale, showBackground/backgroundColor, locale, uiMode dark bit), @PreviewParameter, @RoboComposePreviewOptions manual clock variations (one test per variation), annotation filtering with @RoboPreviewExclude/@RoboPreviewInclude, custom testers via testerQualifiedClassName with a composable-scope Capturer, and JUnit TestRule injection via testRuleFactory. device is not applicable on desktop.

If one module enables both the Robolectric and desktop generators, Roborazzi fails with a configuration error unless separateOutputDirs = true — the two would otherwise silently overwrite each other's goldens.

See the documentation and the sample project.

Huge thanks to @​sergio-sastre — ComposablePreviewScanner's clean pure-JVM design is what made this feature possible.

Documentation restructuring

The documentation was reorganized for easier navigation (#​887#​895): UI tree dump, GIF and video, and GitHub Actions now have their own pages, and the remaining topics (build setup, how to use, Compose Multiplatform, preview support) were pruned of duplicated content. Documentation only — no code changes.

roborazzi-annotations is now multiplatform

roborazzi-annotations is published as a Kotlin Multiplatform library (Android, JVM, iOS) so the marker annotations and @RoboComposePreviewOptions can live in commonMain (#​900). The Maven coordinate and every API signature are unchanged; only the packaging changed. If you consume it through Gradle (as testImplementation(...) / KMP source-set dependencies), nothing to do.

What's Changed

Full Changelog: takahirom/roborazzi@1.69.0...1.70.0

v1.69.0

Compare Source

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#​885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE]
The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

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:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "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 n values in the JSON, so an AI agent (or a teammate) can say "element #​3" and look up its bounds:

Annotated Set-of-Mark image

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 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:

  • The sidecars are informational only: they never participate in image comparison and never fail verification. They are written on record and compare/verify (always describing the current run, under the _actual basename) — including on a failing verify, when you need them most.
  • Per-test configuration: RoborazziOptions(uiTreeDumpOptions = UiTreeDumpOptions(...)), with a customizable numbering predicate (isAnnotatable) and annotateImage = false to write only the JSON.
  • Zero cost and zero behavior change when off (the default) — record output is byte-identical to 1.68.0, and all existing APIs are unchanged (additions only).
Fixes
  • WebP golden files could be corrupted when re-recording a smaller image over an existing file: ImageOutputStream doesn'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.0

Compare Source

Compose Testing v2 (ui-test-junit4 v2) 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

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested review from cka-dev and romanofranz as code owners March 24, 2026 01:03
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 1337fab to 547e905 Compare March 26, 2026 17:58
@renovate renovate Bot changed the title fix(deps): update all dependencies Update all dependencies Apr 8, 2026
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 32a500f to 00e890f Compare April 13, 2026 14:15
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from 442165d to bb9b5cc Compare April 23, 2026 09:06
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from f152fcb to c23e8c2 Compare April 28, 2026 14:07
@renovate
renovate Bot force-pushed the renovate/all branch 8 times, most recently from ad37f5c to 3248902 Compare May 12, 2026 18:49
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 2703f37 to 54f523d Compare May 15, 2026 11:10
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from b701c59 to 747c66b Compare May 27, 2026 12:18
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 2c8dab6 to 096e652 Compare June 10, 2026 03:35
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from 5e01c25 to 78d3a1e Compare June 17, 2026 23:00
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 36624e8 to 4373d54 Compare June 22, 2026 11:21
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 1b2ee0e to 4b63625 Compare June 26, 2026 17:37
@renovate
renovate Bot force-pushed the renovate/all branch 7 times, most recently from cd29b0e to 7aebe25 Compare July 10, 2026 18:01
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from 218ef48 to 1b244a5 Compare July 18, 2026 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants