Update all dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Adoption	Passing	Confidence
gradle (source)		minor	8.11.1 -> 8.12
io.github.takahirom.roborazzi	plugin	minor	1.37.0 -> 1.39.0
io.github.takahirom.roborazzi:roborazzi-accessibility-check	dependencies	minor	1.37.0 -> 1.39.0
io.github.takahirom.roborazzi:roborazzi	dependencies	minor	1.37.0 -> 1.39.0
org.jetbrains.kotlinx:kotlinx-serialization-json	dependencies	minor	1.7.3 -> 1.8.0
org.jetbrains.kotlinx:kotlinx-coroutines-test	dependencies	patch	1.10.0 -> 1.10.1
org.jetbrains.kotlinx:kotlinx-coroutines-guava	dependencies	patch	1.10.0 -> 1.10.1
org.jetbrains.kotlinx:kotlinx-coroutines-android	dependencies	patch	1.10.0 -> 1.10.1
org.jetbrains.kotlinx:kotlinx-coroutines-core	dependencies	patch	1.10.0 -> 1.10.1
com.google.dagger.hilt.android	plugin	minor	2.53.1 -> 2.54
com.google.dagger:hilt-core	dependencies	minor	2.53.1 -> 2.54
com.google.dagger:hilt-compiler	dependencies	minor	2.53.1 -> 2.54
com.google.dagger:hilt-android-testing	dependencies	minor	2.53.1 -> 2.54
com.google.dagger:hilt-android	dependencies	minor	2.53.1 -> 2.54
com.android.tools:desugar_jdk_libs	dependencies	patch	2.1.3 -> 2.1.4

---

Release Notes

gradle/gradle (gradle)

v8.12

Compare Source

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

v1.39.0

Compare Source

Bug Fixes

Diff screenshots are now as large as the largest of the two compared screenshots

Previously, when the size of a screenshot changed (e.g., became smaller), the image diff would not appear because it was based on the minimum size of each screenshot. This has been fixed so that the diff is now based on the largest of the two compared screenshots. Thank you for reporting this issue, @​outadoc!

Report HTML's image order is now deterministic

The image order in the HTML report used to be random. Thanks to @​mannodermaus, it is now sorted by name.

OpenAiAiAssertionModel is now Gemini compatible

Gemini has a compatibility mode with the OpenAI API (https://ai.google.dev/gemini-api/docs/openai). By using https://generativelanguage.googleapis.com/v1beta/openai/ as the base URL, we can essentially use Gemini. However, some properties are different, so we had to modify the OpenAiAiAssertionModel to be compatible with Gemini.

I'm currently developing another library called Arbigent, an AI agent testing framework. I'm planning to add an AI image assertion feature using Roborazzi's AI-Powered Image Assertion, and I needed this compatibility for that. This isn't directly related to this project, but if you're interested in testing, check it out: https://github.com/takahirom/arbigent

What's Changed

• [No library update for users] Update dependency androidx.compose.ui:ui-test to v1.7.6 by @​renovate in https://github.com/takahirom/roborazzi/pull/596
• [No library update for users] Update JetBrains/writerside-github-action digest to b96c8e6 by @​renovate in https://github.com/takahirom/roborazzi/pull/561
• Sort capture results to achieve deterministic order in HTML report by @​mannodermaus in https://github.com/takahirom/roborazzi/pull/622
• Refactor buildContextData by @​takahirom in https://github.com/takahirom/roborazzi/pull/624
• Show diff when size changed by @​takahirom in https://github.com/takahirom/roborazzi/pull/625
• Make OpenAiAiAssertionModel gemini API compatible by @​takahirom in https://github.com/takahirom/roborazzi/pull/626

Full Changelog: takahirom/roborazzi@1.38.0...1.39.0

v1.38.0

Compare Source

Bugfix

Fix: Bug preventing the revival of deleted screenshot images

Thanks to @​pedromfmachado's contribution, we've addressed a bug where deleted screenshot test images would be erroneously revived. Previously, when screenshot tests were removed and their corresponding images deleted from the output directory, running the record task again would cause the Roborazzi Gradle task to recreate the removed images. While this could be temporarily resolved with roborazzi.cleanupOldScreenshots=true, that approach was undesirable as it would also remove images when test filters were used. This was a complex issue to solve, and we extend our gratitude to @​pedromfmachado for the fix.

Fix: Made screenshot dump deterministic

We have a dump feature that allows us to check the properties or hierarchy of views or composables in an image. We sorted the properties to ensure a deterministic output. Thanks to @​siarhei-luskanau for this contribution.

New Feature

Feature: Added RoborazziComposeActivityThemeOption

Previously, changing the theme of RoborazziTransparentActivity was not possible. We have now deprecated RoborazziTransparentActivity and renamed it to RoborazziActivity. Additionally, we added RoborazziComposeActivityThemeOption to enable changing the Activity's theme. Thank you again, @​pedromfmachado, for this feature.

You can now change the Activity theme like this:

 @​OptIn(ExperimentalRoborazziApi::class)
 @​Test
 fun whenNonTransparentThemeItShouldHaveNonTransparentBackground() {
   captureRoboImage(
     roborazziComposeOptions = RoborazziComposeOptions {
       activityTheme(android.R.style.Theme_Material_Light)
     }
   ) {
     Text("This composable function should NOT have transparent background!")
   }
 }

What's Changed

• Sort key order of ComposePrintToString to stabilize output in Dump screenshots. by @​siarhei-luskanau in https://github.com/takahirom/roborazzi/pull/611
• Added RoborazziComposeActivityThemeOption by @​pedromfmachado in https://github.com/takahirom/roborazzi/pull/612
• [Code Style] Add JetCodeStyleSettings to codestyle setting by @​takahirom in https://github.com/takahirom/roborazzi/pull/614
• Removing files from intermediate dir to prevent old screenshots from reappearing by @​pedromfmachado in https://github.com/takahirom/roborazzi/pull/616
• Rename theme() to activityTheme() by @​takahirom in https://github.com/takahirom/roborazzi/pull/617

New Contributors

• @​pedromfmachado made their first contribution in https://github.com/takahirom/roborazzi/pull/612

Full Changelog: takahirom/roborazzi@1.37.0...1.38.0

Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)

v1.8.0

==================

This is a release candidate for the next version. It is based on Kotlin 2.1.0 and includes a few new features, as well
as bugfixes and improvements:

@JsonIgnoreUnknownKeys annotation

Previously, only global setting JsonBuilder.ignoreUnknownKeys controlled whether Json parser would throw exception if
input contained a property that was not declared in a @Serializable class.
There were a lot of complaints that this setting is not
flexible enough.
To address them, we added new @JsonIgnoreUnknownKeys annotation that can be applied on a per-class basis.
With this annotation, it is possible to allow unknown properties for annotated classes, while
general decoding methods (such as Json.decodeFromString and others) would still reject them for everything else.
See details in the corresponding PR.

Stabilization of SerialDescriptor API and @SealedSerializationApi annotation

SerialDescriptor, SerialKind, and related API has been around for a long time and has proven itself useful.
The main reason @ExperimentalSerializationApi was on SerialDescriptor's properties is that we wanted to discourage
people from subclassing it.
Fortunately, Kotlin 2.1 provides a special mechanism for such a
case — SubclassOptInRequired.
New kotlinx.serialization.SealedSerializationApi annotation designates APIs
as public for use, but closed for implementation — the case for SerialDescriptor, which is a non-sealed interface for
technical reasons.
Now you can use most of SerialDescriptor and its builders API without the need to opt-in into experimental
serialization API.
See the PR for more details.

Note: All SerialKinds are stable API now, except PolymorphicKind — we may want to expand it in the future.

Generate Java 8's default method implementations in interfaces

TL;DR This change ensures better binary compatibility in the future for library. You should not experience any
difference from it.

kotlinx.serialization library contains a lot of interfaces with default method implementations. Historically, Kotlin
compiled a synthetic DefaultImpls class for them.
Starting from Kotlin 1.4,
it was possible to compile them using as Java 8's default methods to ensure
that new methods can still be added to interfaces without the need for implementors to recompile.
To preserve binary compatibility with existing clients, a special all-compatbility mode is supported in compiler
to generate both default methods and synthetic DefaultImpls class.

Now, kotlinx.serialization finally makes use of this all-compatibility mode,
which potentially allows us to add new methods to interfaces such as SerialDescriptor, Encoder, Decoder, etc.,
without breaking existing clients. This change is expected to have no effect on existing clients, and no action from
your side is required.
Note that Kotlin 2.2 plans to enable all-compatibility
mode by default.

Other bugfixes and improvements

• Correctly skip structures with Cbor.ignoreUnknownKeys setting (#​2873)
• Handle missing system property without NPE (#​2867)
• Fixed keeping INSTANCE field and serializer function for serializable objects in R8 full mode (#​2865)
• Correctly parse invalid numbers in JsonLiteral.long and other extensions (#​2852)
• Correctly handle serial name conflict for different classes in SerializersModule.overwriteWith (#​2856)
• Add inline reified version of encodeToString as a Json member to streamline the experience for newcomers. (#​2853)
• Do not check kind or discriminator collisions for subclasses' polymorphic serializers if Json.classDiscriminatorMode
  is set to NONE (#​2833)

Kotlin/kotlinx.coroutines (org.jetbrains.kotlinx:kotlinx-coroutines-test)

v1.10.1

Compare Source

• Fixed binary incompatibility introduced for non-JVM targets in #​4261 (#​4309).

google/desugar_jdk_libs (com.android.tools:desugar_jdk_libs)

v2.1.4

• Fix Narrow non Standalone Week Names on some locales. SIMPLIFIED_CHINESE and
  TRADITIONAL_CHINESE is on the last code point convention for narrow format.
  This is a follow up to 2.1.3 using the same values as Standalone Week Names.

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

---

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

---

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

[SimonMarquis]

@dturner not sure why @renovate-bot keeps rebasing the PR (multiple times each day) 🤔
It is currently configured to rebase only when behind base branch, which is not the case. Any idea why does it do that?