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 •
edited
Loading

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 v6 → v7 age confidence
actions/setup-java action major v5 → v6 age confidence
gradle (source) minor 9.4.1 → 9.7.1 age confidence
gradle/actions action major v5 → v6 age confidence
io.github.takahirom.roborazzi plugin minor 1.59.0 → 1.73.0 age confidence
io.github.takahirom.roborazzi:roborazzi-junit-rule dependencies minor 1.59.0 → 1.73.0 age confidence
io.github.takahirom.roborazzi:roborazzi-compose dependencies minor 1.59.0 → 1.73.0 age confidence
io.github.takahirom.roborazzi:roborazzi dependencies minor 1.59.0 → 1.73.0 age confidence
org.jetbrains.kotlinx:kotlinx-coroutines-test dependencies minor 1.10.2 → 1.11.0 age confidence
org.mockito.kotlin:mockito-kotlin dependencies minor 6.2.3 → 6.3.0 age confidence
org.jetbrains.kotlin.plugin.compose plugin minor 2.3.20 → 2.4.10 age confidence
com.google.devtools.ksp (source) plugin patch 2.3.6 → 2.3.11 age confidence
com.google.protobuf:protobuf-javalite (source) dependencies minor 4.34.0 → 4.36.1 age confidence
androidx.navigation:navigation-compose (source) dependencies minor 2.9.7 → 2.10.0 age confidence
androidx.navigation:navigation-runtime-ktx (source) dependencies minor 2.9.7 → 2.10.0 age confidence
androidx.compose.material3.adaptive:adaptive-navigation-android (source) dependencies minor 1.2.0 → 1.3.0 age confidence
androidx.lifecycle:lifecycle-runtime-compose (source) dependencies minor 2.10.0 → 2.11.0 age confidence
androidx.lifecycle:lifecycle-viewmodel-compose (source) dependencies minor 2.10.0 → 2.11.0 age confidence
androidx.compose:compose-bom dependencies minor 2026.03.00 → 2026.08.00 age confidence
com.google.dagger.hilt.android plugin minor 2.59.2 → 2.60.1 age confidence
androidx.lifecycle:lifecycle-runtime-ktx (source) dependencies minor 2.10.0 → 2.11.0 age confidence
com.google.protobuf:protoc (source) dependencies minor 4.34.0 → 4.36.1 age confidence
org.jetbrains.kotlinx:kotlinx-serialization-json dependencies minor 1.10.0 → 1.11.0 age confidence
org.jetbrains.kotlin.plugin.serialization plugin minor 2.3.20 → 2.4.10 age confidence
androidx.core:core-ktx (source) dependencies minor 1.18.0 → 1.19.0 age confidence
org.jetbrains.kotlin.android plugin minor 2.3.20 → 2.4.10 age confidence
androidx.hilt:hilt-navigation-compose (source) dependencies minor 1.3.0 → 1.4.0 age confidence
com.google.dagger:hilt-android-testing dependencies minor 2.59.2 → 2.60.1 age confidence
com.google.dagger:hilt-android-compiler dependencies minor 2.59.2 → 2.60.1 age confidence
com.google.dagger:hilt-android dependencies minor 2.59.2 → 2.60.1 age confidence
androidx.compose.foundation:foundation (source) dependencies minor 1.10.5 → 1.12.0 age confidence
com.google.protobuf plugin minor 0.9.6 → 0.10.0 age confidence
io.coil-kt.coil3:coil-network-okhttp dependencies minor 3.4.0 → 3.6.1 age confidence
io.coil-kt.coil3:coil-compose dependencies minor 3.4.0 → 3.6.1 age confidence
androidx.appcompat:appcompat-resources (source) dependencies minor 1.7.1 → 1.8.0 age confidence
androidx.appcompat:appcompat (source) dependencies minor 1.7.1 → 1.8.0 age confidence
com.android.library (source) plugin minor 9.1.0 → 9.4.0 age confidence
com.android.application (source) plugin minor 9.1.0 → 9.4.0 age confidence

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

actions/setup-java (actions/setup-java)

v6.0.0

Compare Source

gradle/gradle (gradle)

v9.7.1

Compare Source

v9.7.0

Compare Source

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.3.0

Compare Source

Highlights

Enhanced Caching: Windows fixes and a cache-protocol bump

This release updates gradle-actions-caching to v1.0.0 (up from v0.7.0), which fixes two significant caching defects, both most visible on Windows:

  • Cache entries failed to store at all on Windows.. Every entry failed
    with Path Validation Error: Path(s) specified in the action for caching do(es) not exist, even though the Gradle User Home was fully intact. Nothing was stored, so
    every downstream job ran against an empty Gradle User Home. The cause was a nested,
    unpatched copy of @actions/glob combined with a silently swallowed require() in
    the bundle, which left Windows path separators unnormalized.

  • Cache cleanup deleted instrumented jars that were in use. A bug in key
    hashing for paths shorter than 64 characters made cleanup judge freshly created
    caches/jars-9 entries as unused and remove them, so the instrumented-jars entry
    was never saved and every job re-instrumented its classpaths.

    Also included: cache entry names are now consistent between the save and restore
    reports — restore previously fell back to showing the raw glob pattern (e.g.
    /home/runner/.gradle/caches/modules-*/files-*/*/*/*/*/) instead of dependencies.

[!IMPORTANT]
Existing cache entries are invalidated by this release. The cache protocol
version was bumped to v2, so the first run after upgrading will be a cache miss
and will repopulate the cache. No configuration changes are required.

Basic caching warns instead of failing silently

The basic (open-source) caching provider now emits a warning and reports
(Entry not saved: save failed) in the Job Summary when a cache save fails, rather
than reporting success (#​1028).

Dependency submission works with Isolated Projects

dependency-submission now disables Isolated Projects via a promoted property, so
dependency graph generation works on builds that enable it (#​1025). Thanks to @​reinsch82 for the contribution.

Updated defaults
  • Injected Develocity Gradle plugin: 4.4.2 → 4.5.0
  • 36 new known-good wrapper checksums added for wrapper-validation

What's Changed

New Contributors

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

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

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

v1.73.0

Compare Source

Performance
  • Identical screenshots skip the per-pixel comparison. A passing test compares an image identical to its golden, which is the common case — the backing rasters are now compared with bulk integer comparisons, falling back to the ImageComparator only 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
  • Build cache relocatability with 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.0

Compare Source

New: Subdirectory naming strategies for screenshot paths

Two new roborazzi.record.namingStrategy options organize screenshots into directories instead of one flat folder of fully-qualified file names (#​909, fixes #​801):

# com.example.myapp.ui/SomeClass.method.png — the package as a single directory level
roborazzi.record.namingStrategy=testPackageDirAndClassAndMethod

# com/example/myapp/ui/SomeClass.method.png — the package as nested directories
roborazzi.record.namingStrategy=testNestedPackageDirAndClassAndMethod

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 / _actual images mirror the golden's subdirectory. This matters because the package no longer appears in the leaf file name with the *Dir strategies — 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 via RoborazziRule. The three existing strategies produce byte-for-byte identical paths as before, so nothing changes unless you opt in.

Fixes
  • Wrong screenshot path on Windows. With 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.0

Compare 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.

  • The dump was empty for 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.defaultChildVisitor only descended into semantics for an AbstractComposeView, but this path passes the AndroidComposeView as the capture root: not an AbstractComposeView, just a ViewGroup that itself implements ViewRootForTest. Traversal fell through to the plain ViewGroup branch and stopped. It now descends for a ViewRootForTest as well, which also restores the Compose boxes in captureType = Dump images on this path (#​914, fixes #​913). Thank you @​danielkatfavor for the clear report with the exact sidecar output!
  • CustomActions serialization was non-deterministic. A CustomAccessibilityAction's action lambda is serialized via toString(), 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 as CustomAccessibilityAction(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

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 prev

✂ 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 7 times, most recently from cd29b0e to 7aebe25 Compare July 10, 2026 18:01
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from 1b244a5 to 19e5362 Compare July 20, 2026 10:55
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 2b9b28b to 80afae7 Compare July 29, 2026 19:00
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from f20a4d9 to 46b74c1 Compare August 12, 2026 18:35
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from b676eb5 to 83c9c8e Compare August 22, 2026 15:53
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from d4aaced to 43b5379 Compare August 26, 2026 17:42
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from c35494f to 8d004e7 Compare September 1, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cka-dev cka-dev Awaiting requested review from cka-dev cka-dev is a code owner
@romanofranz romanofranz Awaiting requested review from romanofranz romanofranz is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants