Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update test.roborazzi to v1.40.1 #829

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update test.roborazzi to v1.40.1 #829

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 11, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.github.takahirom.roborazzi 1.3.0 -> 1.40.1 age adoption passing confidence
io.github.takahirom.roborazzi:roborazzi-compose 1.3.0 -> 1.40.1 age adoption passing confidence
io.github.takahirom.roborazzi:roborazzi-junit-rule 1.3.0 -> 1.40.1 age adoption passing confidence
io.github.takahirom.roborazzi:roborazzi 1.3.0 -> 1.40.1 age adoption passing confidence

Release Notes

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

v1.40.1

Compare Source

New Feature: Add AiAssertionOptions.AssertionImageType to Support Actual Image Validation

We previously introduced AI Assertion which utilizes a comparison image for assertions. However, we noticed the current implementation struggled with optimal performance due to image size constraints, where sufficient context size is crucial for accurate AI analysis. To address this, we've introduced the AssertionImageType parameter. You can now specify the image type via AiAssertionOptions.

  sealed interface AssertionImageType {
    class Comparison : AssertionImageType
    class Actual : AssertionImageType
  }
Bug Fix: Improved AI Assertion OpenAI API Error Messaging

Previously, API error messages were unclear and unhelpful. We've revamped the error handling to provide meaningful feedback, including proper API status details.

Before:

Fields [object, created, model, choices] are required for type with serial name 'com.github.takahirom.roborazzi.ChatCompletionResponse', but they were missing at path: $
kotlinx.serialization.MissingFieldException: Fields [object, created, model, choices] are required for type with serial name 'com.github.takahirom.roborazzi.ChatCompletionResponse', but they were missing at path: $

After:

Caused by: java.util.concurrent.ExecutionException: com.github.takahirom.roborazzi.AiAssertionApiException: {
    "error": {
        "message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
        "type": "invalid_request_error",
        "param": null,
        "code": null
    }
}
Changes from 1.40.0

We initially introduced AssertionImageType.Reference instead of AssertionImageType.Actual in version 1.40.0. This was a mistake, as it referred to old images, a feature we've determined to be unnecessary. We have corrected this in the current release by using AssertionImageType.Actual.

What's Changed

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

v1.40.0

Compare Source

Please refer to https://github.com/takahirom/roborazzi/releases/tag/1.40.1

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

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
New Contributors

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

v1.37.0

Compare Source

Bug Fixes and Workarounds
Compose AlertDialog Support

Support for capturing Alert Dialogs has been fixed, ensuring correct screenshot display. captureScreenRoboImage(), which merges all windows, is now used only when multiple windows are present. Thanks to @​ashughes for reporting this and to @​mhidaka and @​hiroaki404 for bringing it to my attention at a Japan Android testing event.

image
Workaround for Overlap Handling for SDK 35 Compose Screenshots
Problem

When updating to SDK 35 and using the default theme, the ActionBar is included in screenshots, leading to overlap when using createComposeRule(). This occurs because createComposeRule() uses the default theme by default. Thank you for letting me know about this, @​keyboardsurfer!

I have filed an issue for this: https://issuetracker.google.com/issues/383368165

Why this happens

SDK 35 enforces edge-to-edge display, which means it does not provide automatic padding for the ActionBar.

How Roborazzi currently workarounds this

Roborazzi now automatically hides the ActionBar when taking screenshots on SDK 35 and higher. This functions similarly to view.getActivity()?.actionBar?.hide(). However, this workaround may cause performance issues and should not be relied upon. Roborazzi outputs warning logs with alternative suggestions. Thank you to @​sergio-sastre for advising on this workaround!

If you need to include the ActionBar in screenshots, Roborazzi provides a flag, roborazzi.compose.actionbar.overlap.fix=false, that can be added to your gradle.properties file.

What should we do?

A permanent solution will likely require changes from Google. In the meantime, adding <application android:theme="@&#8203;style/android:Theme.Material.Light.NoActionBar" /> to the module's src/test/AndroidManifest.xml file changes the Activity's default theme and resolves the issue. Thank you to @​mattinger for finding this!

https://github.com/takahirom/roborazzi/issues/598#issuecomment-2533372700

Stabilized Output for Dump Screenshots

Thanks to @​siarhei-luskanau for contributing an improvement that reduces unnecessary diffs for the Roborazzi dump feature.

New Features
Add inspectionMode() for Compose Previews

Thanks to @​YusukeMoriJapan's contribution, inspectionMode() is now available in RoborazziComposeOptions. This is particularly useful when working with libraries that have specific preview implementations. This mode is off by default to maintain high fidelity.

Here's how to enable it:

captureRoboImage(
    roborazziComposeOptions = RoborazziComposeOptions {
        inspectionMode(true)
    }
) {
    ...
}
What's Changed
New Contributors

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

v1.36.0

Compare Source

Behavior Changes to roborazzi.outputDir.set(file("somedir")) in build.gradle

Previously, when modifying roborazzi.outputDir, such as setting it to src/screenshots, this option also affected the paths for comparison images, like foo_compare.png. This behavior often caused issues, such as unintentionally saving comparison images to version control systems (e.g., Git). To address this, we have discontinued this behavior. Comparison images are now saved in build/outputs/roborazzi by default, while the behavior for reference images remains unchanged.

For users who wish to customize the path for comparison images, we have introduced a new option: roborazzi.compare.outputDir.

While I don't believe there are strong use cases for this, if you want to save the comparison images in a custom directory as you did before, you can specify roborazzi.compare.outputDir as follows:

roborazzi {
  outputDir.set(file("src/screenshots"))
  compare {
    outputDir.set(file("src/screenshots"))
  }
}

I believe this adjustment will be highly beneficial for most use cases involving changes to outputDir.

[!NOTE]
By default, when you use captureRoboImage("image.png"), the image will be saved as module/image.png.
You can customize the file path strategy for the recorded image. The default strategy is relativePathFromCurrentDirectory. If you select relativePathFromRoborazziContextOutputDirectory, the file will be saved in the output directory specified by roborazzi.outputDir.
This can be configured in your gradle.properties file:

roborazzi.record.filePathStrategy=relativePathFromRoborazziContextOutputDirectory
What's Changed

Full Changelog: takahirom/roborazzi@1.35.0...1.36.0

v1.35.0

Compare Source

Add support for heightDp, widthDp, showBackground, and backgroundColor of Compose Preview parameters

We have introduced Experimental Compose Preview Support in 1.22.0, but it does not yet support all parameters of the @Preview annotation. Thanks to @​sergio-sastre 's pull request, the Experimental Compose Preview Support now includes support for heightDp, widthDp, showBackground, and backgroundColor.

Introduce RoborazziComposeOptions

To accommodate the changes in preview parameters, we’ve made the API more flexible.

We’ve added the RoborazziComposeOptions parameter to ComposablePreview<AndroidPreviewInfo>.captureRoboImage() and the composable function version, captureRoboImage{}. Previously, the API was limited; for example, you couldn’t access the ActivityScenario or the composable function directly. Now, you have full control over these components. Thank you for your code review @​sergio-sastre

Here’s an example of a custom option:

    captureRoboImage(
      roborazziComposeOptions = RoborazziComposeOptions {
        // We have several options to configure the test environment.
        fontScale(2f)
        // We can also configure the activity scenario and the composable content.
        addOption(
          object : RoborazziComposeComposableOption,
            RoborazziComposeActivityScenarioOption {
            override fun configureWithActivityScenario(scenario: ActivityScenario<out Activity>) {
              scenario.onActivity {
                it.window.decorView.setBackgroundColor(Color.BLUE)
              }
            }

            override fun configureWithComposable(content: @&#8203;Composable () -> Unit): @&#8203;Composable () -> Unit {
              return {
                Box(Modifier
                  .padding(10.dp)
                  .background(color = androidx.compose.ui.graphics.Color.Red)
                  .padding(10.dp)
                ) {
                  content()
                }
              }
            }
          }
        )
      },
    ) {
      Text("Hello Compose!")
    }

image

Breaking Change: fun ComposablePreview<AndroidPreviewInfo>.applyToRobolectricConfiguration() is now deprecated and marked as an error

As part of our updates to how composables are configured, the applyToRobolectricConfiguration() function is now deprecated and marked as an error. Instead, you can use one of the following alternatives:

  • previewInfo.toRoborazziComposeOptions().apply(scenario, composeContent)
  • ComposablePreview<AndroidPreviewInfo>.captureRoboImage(roborazziComposeOptions)

We believe this feature is not widely used, and the migration should be straightforward. However, if you encounter any issues, please don’t hesitate to reach out.

Breaking Change: Composable captureRoboImage{} Behavior Change

We intended to use a transparent background for the Compose captureRoboImage function, but it was not applied due to Robolectric's resource merging mechanism. We have fixed this behavior; however, this change will result in altered screenshots. You can now specify the background in the new RoborazziComposeOptions as we had previously.

@&#8203;Test
fun captureComposeLambdaImage() {
    captureRoboImage(
        roborazziComposeOptions = RoborazziComposeOptions {
            background(
                showBackground = true
            )
        }
    ) {
        Text("Hello Compose!")
    }
}
What's Changed

Full Changelog: takahirom/roborazzi@1.34.0...1.35.0

v1.34.0

Compare Source

Stabilize RoborazziOptions and RoborazziRule.Options

RoborazziOptions and RoborazziRule.Options were not annotated with ExperimentalRoborazziApi, but their constructor parameters had the annotation. This caused ExperimentalRoborazziApi to be unintentionally exposed. To address this, we have separated constructors for stable parameters. Additionally, within Roborazzi samples, we have enabled allWarningsAsErrors = true to ensure that any unexpected exposure can be promptly identified.
Thank you for reporting this issue and for your code review, @​colinrtwhite!

Fixes for Accessibility Checks

We introduced Experimental Accessibility Test Framework checks in version 1.33.0.
Thanks to @​yschimke's contribution, several fixes have been implemented for accessibility checks, including check suppression and improved logging.

What's Changed

Full Changelog: takahirom/roborazzi@1.33.0...1.34.0

v1.33.0

Compare Source

Experimental Accessibility Test Framework checks

Thanks to @​yschimke's contribution, we now have a library that integrates accessibility checks into Roborazzi. It uses the Accessibility Test Framework to ensure accessibility.

Please add the library dependency:

testImplementation("io.github.takahirom.roborazzi:roborazzi-accessibility-check:[version]")

https://github.com/takahirom/roborazzi/tree/main/roborazzi-accessibility-check

Configure in Junit Rule
  @&#8203;get:Rule
  val roborazziRule = RoborazziRule(
    composeRule = composeTestRule,
    captureRoot = composeTestRule.onRoot(),
    options = Options(
      roborazziAccessibilityOptions = RoborazziATFAccessibilityCheckOptions(
        checker = RoborazziATFAccessibilityChecker(
          checks = setOf(NoRedTextCheck()),
          suppressions = matchesElements(withTestTag("suppress"))
        ),
        failureLevel = RoborazziATFAccessibilityChecker.CheckLevel.Warning
      ),
      // If you want to automatically check accessibility after a test, use AccessibilityCheckAfterTestStrategy.
      accessibilityCheckStrategy = AccessibilityCheckAfterTestStrategy(),
    )
  )
Add accessibility checks
composeTestRule.onNodeWithTag("nothard").checkRoboAccessibility(
  // If you don't specify options, the options in RoborazziRule will be used.
  roborazziATFAccessibilityCheckOptions = RoborazziATFAccessibilityCheckOptions(
    checker = RoborazziATFAccessibilityChecker(
      preset = AccessibilityCheckPreset.LATEST,
    ),
    failureLevel = RoborazziATFAccessibilityChecker.CheckLevel.Warning
  )
)

Not only is this library designed to make our app accessible to everyone, but I also believe that AI agent testing will be a future trend, and we want to prepare for it. I think this could help make our app accessible to AI as well, enabling agents to interact with it, such as clicking on image buttons using content descriptions. Additionally, we can create custom checks, like NoRedTextCheck, specifically for AI.

What's Changed

Full Changelog: takahirom/roborazzi@1.32.2...1.33.0

v1.32.2

Compare Source

WebP Image Comparison Improvements

Improved handling for transparent pixels in WebP image comparisons. Previously, transparent pixels in WebP images were sometimes returned with unexpected color values (e.g., r = 1, g = 0, b = 0, a = 0), which caused inconsistencies in image comparisons. The comparison logic now correctly handles transparent pixels by interpreting them as fully transparent black (r = 0, g = 0, b = 0, a = 0) to ensure consistent results across comparisons.

Special thanks to @​ArcaNO93 for identifying and reporting this issue!

What's Changed

Full Changelog: takahirom/roborazzi@1.32.1...1.32.2

v1.32.1

Compare Source

Experimental WebP support and other image formats

Now, you can set roborazzi.record.image.extension to webp in your gradle.properties file to generate WebP images.

roborazzi.record.image.extension=webp

To enable WebP support, add testImplementation("io.github.darkxanter:webp-imageio:0.3.3") to your build.gradle.kts file.
WebP is a lossy image format by default, which can make managing image differences challenging. To address this, we provide a lossless WebP image feature.
WebP lossless images are reported to be 26% smaller in size compared to PNGs.

onView(ViewMatchers.withId(R.id.textview_first))
  .captureRoboImage(
    roborazziOptions = RoborazziOptions(
      recordOptions = RoborazziOptions.RecordOptions(
        imageIoFormat = LosslessWebPImageIoFormat(),
      ),
    )
  )

You can also use other image formats by implementing your own AwtImageWriter and AwtImageLoader.

data class JvmImageIoFormat(
  val awtImageWriter: AwtImageWriter,
  val awtImageLoader: AwtImageLoader
) : ImageIoFormat

Thank you, @​ArcaNO93, for providing this suggestion and the code review!

Adjustments to AI-Powered Image Assertion

In version 1.30.0, we introduced Roborazzi AI-Powered Image Assertion.
We made some adjustments to the AI-Powered Image Assertion

  • The OpenAiAiAssertionModel, which utilizes OpenAI APIs, previously lacked a timeout specification, leading to frequent timeout issues. We have now implemented a customizable timeout setting.
  • The provideRoborazziContext().option was marked as InternalRoborazziApi despite being documented in the README. We have now changed it to ExperimentalRoborazzi API.
Changes from 1.32.0

API Key Masking in Logs for OpenAiAiAssertionModel
For users enabling logging through OpenAiAiAssertionModel.loggingEnabled, API keys in log outputs are now masked to improve security. Previously, API keys could appear in logs, which could unintentionally expose them, especially in test reports. With this update, sensitive data is automatically masked, helping users avoid accidental exposure.

What's Changed

Full Changelog: takahirom/roborazzi@1.31.0...1.32.1

v1.32.0

Compare Source

Please refer to the 1.32.1 release at https://github.com/takahirom/roborazzi/releases/tag/1.32.1

v1.31.0

Compare Source

Added Experimental Support for Cleaning Up Old Screenshots

This release introduces the roborazzi.cleanupOldScreenshots=true option in gradle.properties, allowing users to automatically remove outdated screenshots. By default, this is set to false to prevent accidental deletions when running filtered tests. Please note that enabling this option may result in unintended deletions when running filtered tests. You can use -Proborazzi.cleanupOldScreenshots=true for CI configurations to clean up screenshots only in CI runs without affecting local settings.
This cleanup implementation may affect the cache mechanism. We have some integration tests in place, but if you notice any issues, please let us know.
Thank you, @​JackEblan, for suggesting the cleanup feature!

Improve AI Assertion Error Message

In the previous release, we introduced Roborazzi AI-Powered Image Assertion.
When an AI assertion fails, it’s important to review the screenshots to understand what went wrong with the images. Therefore, I enhanced the error message to include the file paths of the images.

image

What's Changed

Full Changelog: takahirom/roborazzi@1.30.1...1.31.0

v1.30.1

Compare Source

Roborazzi AI-Powered Image Assertion 🤖 ✨

Roborazzi introduces an experimental AI-powered image assertion feature to simplify and scale the process of verifying screenshot test content. This feature helps automate tedious visual checks by comparing images based on customizable AI prompts, utilizing either the Gemini API or OpenAI API. It only activates when images differ, conserving resources. Additionally, manual AI assertion is available, allowing users to leverage local language models without external dependencies.
We don't include Gemini or OpenAI dependencies in the roborazzi module. To use these models, you can add either roborazzi-ai-gemini or roborazzi-ai-openai as dependencies.

  onView(ViewMatchers.isRoot())
    .captureRoboImage(
      roborazziOptions = provideRoborazziContext().options.addedAiAssertion(
        assertionPrompt = "The screen should have a PREVIOUS button",
      )
   )

For more information, please check out this documentation page:
https://takahirom.github.io/roborazzi/ai-powered-image-assertion.html

Roborazzi Compose Preview Support now supports the device parameter@Preview(device = "") 📱

Roborazzi Compose Preview Support uses ComposablePreviewScanner and ComposablePreviewScanner now supports parsing device parameter. It is introduced to Compose Preview Support. Thank you, @​sergio-sastre, for developing this adapter and integrating it with Roborazzi.
If you are using Roborazzi Compose Preview Support with device parameters, you need to update your ComposablePreviewScanner to version 0.4.0.

Remove Context Receiver from roborazzi-desktop ♻️

The Context Receiver in Kotlin is now deprecated, so we need to remove it. The context(DesktopComposeUiTest) requirement existed because the file compose/ui/ui-test/src/skikoMain/kotlin/androidx/compose/ui/test/SkikoImageHelpers.kt was previously unavailable, necessitating the use of DesktopComposeUiTest. Now that SkikoImageHelpers is available, we can eliminate the context(DesktopComposeUiTest) requirement.

This functionality was introduced in the Compose Multiplatform core repository (commit 1664fba: JetBrains/compose-multiplatform-core@1664fba) and has been supported since Compose Multiplatform version 1.5.12 (https://github.com/JetBrains/compose-multiplatform-core/releases/tag/v1.5.12).
Please note that this may be a breaking change if you are using Compose Multiplatform version 1.5.12 or earlier.

Changes from 1.30.0

  • Breaking changes to 1.30.0:
    Renamed parameter assertPrompt to assertionPrompt.

  • Use max_tokens instead of max_completion_tokens for the OpenAI API:
    Although max_tokens has been deprecated, we still need to use it in certain environments.

What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.29.0...1.30.0
Full Changelog: takahirom/roborazzi@1.30.0...1.30.1

v1.30.0

Compare Source

Please refer to version 1.30.1

v1.29.0

Compare Source

Bug Fixes

We introduced an image diff percentage in the report. However, when the screenshot's image size changes, there was an issue causing Roborazzi to crash. We have added a test for image size changes and fixed this problem. Thank you for reporting this. @​Daiji256

Breaking Change

We are migrating our codebase to Kotlin Multiplatform (KMP). Roborazzi uses dropbox/differ to calculate image diffs. Thanks to @​eyedol 's contribution, differ now supports KMP for iOS, so we updated dropbox/differ. Some KMP migration is still needed for iOS support.

What's Changed

Full Changelog: takahirom/roborazzi@1.28.0...1.29.0

v1.28.0

Compare Source

Breaking changes

Now we are using gradlePropertiesPrefixedBy to support Gradle Isolated Projects in the Roborazzi Gradle Plugin. This API requires Gradle 8.0. Gradle 8.0 was released early last year, and most projects I know use 8.0 or higher, so Roborazzi is going to use this API. If anyone can't use this, please let me know.
@​trevjonez, thank you for telling me what we need to do to support this.
Currently, we aren't able to ensure compatibility with Gradle Isolated Projects, but this could bring some progress.

Adapting to the new ComposablePreviewScanner version

We are using ComposablePreviewScanner for Compose Preview Support. The ComposablePreviewScanner is now on Maven Central 🎉 and the group name of the libraries has changed. We have adapted to the new version and don't show errors when not using Jitpack and using the new packages.

What's Changed

Full Changelog: takahirom/roborazzi@1.27.0...1.28.0

v1.27.0

Compare Source

Bugfix for Compose Preview Support

As Compose Preview Support don't automatically add dependencies to maintain a single source of

Configuration

📅 Schedule: Branch creation - "* 0-3 * * *" in timezone Asia/Seoul, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • 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 a review from jisungbin as a code owner August 11, 2023 16:38
@renovate renovate bot enabled auto-merge (rebase) August 11, 2023 16:38
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 2 times, most recently from 71edbfc to 37679f0 Compare August 17, 2023 19:45
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 3 times, most recently from d69422f to 767e6bc Compare August 26, 2023 06:16
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 6 times, most recently from 91741b8 to aea3340 Compare September 6, 2023 22:35
@jisungbin jisungbin removed their request for review September 7, 2023 00:47
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 4 times, most recently from 47c80b8 to 6f0fb26 Compare September 14, 2023 18:12
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 2 times, most recently from 8ba7e81 to 7ae5a9c Compare September 18, 2023 07:17
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.4.0 chore(deps): update test.roborazzi to v1.5.0 Sep 18, 2023
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 3 times, most recently from 1f0f766 to ef8b1f5 Compare September 25, 2023 12:14
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 3 times, most recently from 69b04cb to 04f0f71 Compare October 6, 2023 18:24
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 04f0f71 to e3a9d1d Compare October 8, 2023 06:51
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 753c174 to 44c2d4e Compare November 4, 2024 03:41
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.30.0 chore(deps): update test.roborazzi to v1.30.1 Nov 4, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 44c2d4e to 8281530 Compare November 5, 2024 13:42
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.30.1 chore(deps): update test.roborazzi to v1.31.0 Nov 5, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 8281530 to f652ef4 Compare November 7, 2024 05:09
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.31.0 chore(deps): update test.roborazzi to v1.32.0 Nov 7, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from f652ef4 to 8ce9c5b Compare November 7, 2024 07:39
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.32.0 chore(deps): update test.roborazzi to v1.32.1 Nov 7, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 8ce9c5b to 84f5148 Compare November 9, 2024 01:28
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.32.1 chore(deps): update test.roborazzi to v1.32.2 Nov 9, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 84f5148 to 106d72e Compare November 21, 2024 11:25
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.32.2 chore(deps): update test.roborazzi to v1.33.0 Nov 21, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 106d72e to aceeff4 Compare November 24, 2024 03:51
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.33.0 chore(deps): update test.roborazzi to v1.34.0 Nov 24, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from aceeff4 to 4e55895 Compare December 8, 2024 04:54
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.34.0 chore(deps): update test.roborazzi to v1.35.0 Dec 8, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 4e55895 to df22b21 Compare December 9, 2024 11:49
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.35.0 chore(deps): update test.roborazzi to v1.36.0 Dec 9, 2024
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.36.0 fix(deps): update test.roborazzi to v1.36.0 Dec 10, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from df22b21 to 2a08992 Compare December 15, 2024 12:09
@renovate renovate bot changed the title fix(deps): update test.roborazzi to v1.36.0 fix(deps): update test.roborazzi to v1.37.0 Dec 15, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 2a08992 to 5529e05 Compare December 23, 2024 10:57
@renovate renovate bot changed the title fix(deps): update test.roborazzi to v1.37.0 fix(deps): update test.roborazzi to v1.38.0 Dec 23, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 5529e05 to 76446ef Compare January 6, 2025 11:17
@renovate renovate bot changed the title fix(deps): update test.roborazzi to v1.38.0 fix(deps): update test.roborazzi to v1.39.0 Jan 6, 2025
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 76446ef to 7518266 Compare January 24, 2025 05:04
@renovate renovate bot changed the title fix(deps): update test.roborazzi to v1.39.0 fix(deps): update test.roborazzi to v1.40.0 Jan 24, 2025
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 7518266 to 7b67227 Compare January 24, 2025 09:02
@renovate renovate bot changed the title fix(deps): update test.roborazzi to v1.40.0 fix(deps): update test.roborazzi to v1.40.1 Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies gradle
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants