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

chore(deps): update test.roborazzi to v1.20.0 #829

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

chore(deps): update test.roborazzi to v1.20.0 #829

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 11, 2023 •
edited

Mend Renovate

This PR contains the following updates:

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

Release Notes

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

v1.20.0

Compare Source

Workflow Enhancement

We use images as inputs for tests, ensuring that the compare and verify tasks function correctly. However, while running record tasks, we do not need the input images. Despite this, these input images invalidate the record task and disable the cache. Therefore, we no longer use input images for record tasks. Thank you, @​lukas-mercari, for informing us and proposing this improvement.

What's Changed

Full Changelog: takahirom/roborazzi@1.19.0...1.20.0

v1.19.0

Compare Source

Bug Fix

I was informed that if you have multiple test suites, the RoborazziPlugin sometimes fails due to concurrent processes. This happens because the cleanup process runs multiple times. Therefore, I made the cleanup process run only once. Thank you for reporting this, @​lukas-mercari.

What's Changed

Full Changelog: takahirom/roborazzi@1.18.0...1.19.0

v1.18.0

Compare Source

Migrating from java.io.File to kotlinx-io

Note: We are not changing the API for users, so the captureRoboImage methods are still using the java.io.File class.
Roborazzi previously used java.io.File for saving and loading files. Although Roborazzi supports iOS, sharing much of the logic is challenging when using java.io.File. Therefore, we have migrated to kotlinx-io.
We are attentive to the Kotlin versions our users employ. We upgraded from version 1.9.21 to 1.9.22 due to a dependency on kotlinx-io. Since Kotlin 1.9.22 was released last year, it should be compatible with most projects.
Thank you, @​eyedol, for your outstanding contribution! Your efforts are greatly appreciated.

|    \--- org.jetbrains.kotlinx:kotlinx-io-core:0.3.3
|         +--- org.jetbrains.kotlinx:kotlinx-io-bytestring:0.3.3
|         |    \--- org.jetbrains.kotlin:kotlin-stdlib:1.9.22 (*)
|         \--- org.jetbrains.kotlin:kotlin-stdlib:1.9.22 (*)
What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.17.0...1.18.0

v1.17.0

Compare Source

Bug Fixes
  • There seemed to be a pattern where ActivityScenario's close was not being called when tests failed, causing leaks, so I used a use block to ensure it is closed properly. @​yschimke, thank you for pointing out this issue.
  • At companies that use Roborazzi on a large scale, there were issues with the output dir not being restored properly due to Configuration cache and other factors, so I simplified the design to make problems less likely to occur.
  • There were occasional errors reporting that a directory did not exist, and I've added code to address this issue. @​lukas-mercari, thank you for your contribution.
What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.16.1...1.17.0

v1.16.1

Compare Source

Bugfix

We removed the setting for the test task's input directory in 1.16.0, but it caused incorrect results in the compare tests. Therefore, I reverted the changes to the test input directory. This bug is now covered by Roborazzi's integration tests.

What's Changed

Full Changelog: takahirom/roborazzi@1.16.0...1.16.1

v1.16.0

Compare Source

Improvements
  • @​lukas-mercari informed me that we can optimize our build-cache strategy by eliminating outdated cache invalidation logic. With this adjustment, Roborazzi's integration test time was reduced from 10 minutes to 6 minutes by utilizing caches. Thanks for the excellent improvement suggestion. This might also help other users' projects. Roborazzi's integration tests cover several use cases, but if you encounter any issues related to caching, please let me know.
  • We have been supporting iOS since the previous version of Roborazzi and want to share code with the iOS sourceset as much as possible. Therefore, we migrated from Gson to Kotlinx.serialization 1.6.3. Thank you for your contribution, @​sanao1006
  • Roborazzi has been supporting accessibility dumps for Android, and we have now added the capability to check the disabled status within these dumps. Thank you for your contribution, @​lukas-mercari !
image
What's Changed

Full Changelog: takahirom/roborazzi@1.15.0...1.16.0

v1.15.0

Compare Source

Improvements
  • Resolved a Race Condition in Roborazzi Gradle Integration Tests: In version 1.14.0, we identified an intermittent issue where images from Roborazzi did not always appear in the output directory during certain test scenarios, particularly when test results were cached. Despite efforts to resolve this in 1.14.0, the issue persisted due to its elusive nature. In this release, we have successfully addressed this problem, ensuring that images are now consistently placed in the output directory under similar conditions. This improvement has been verified through our integration tests. This issue may occur in user projects, so we recommend updating to this version.
    We continue to refine our testing processes to prevent similar issues in future releases.
What's Changed

Full Changelog: takahirom/roborazzi@1.14.0...1.15.0

v1.14.0

Compare Source

Bug fixes

Cache-related Flakiness in Comparison Results: We've identified and resolved an intermittent issue where cached data could sometimes prevent users from seeing comparison results in Roborazzi.
https://github.com/takahirom/roborazzi/pull/323

What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.13.0...1.14.0

v1.13.0

Compare Source

Add experimental, minimal support for iOS in Compose Multiplatform

Roborazzi has supported Compose Desktop, but we hadn't yet supported iOS, which could be a major use case for Compose Multiplatform. Therefore, I have added support for iOS.
Now, you can record, compare, and verify just as you would with Android support.
https://takahirom.github.io/roborazzi/compose-multiplatform.html#experimental-feature-ios-support

ios_button_compare

However, Roborazzi is fundamentally based on the JVM. Currently, we offer only minimal features. If you are interested in helping to improve these features, please take a look at these issues:
https://github.com/takahirom/roborazzi/issues/302 https://github.com/takahirom/roborazzi/issues/305

Changes Affecting Existing Support

To support iOS, we have made some dependency changes for Android and Compose Desktop. I believe these changes will not affect existing behavior. However, if you notice anything, please let me know.

All
Kotlin:
1.8.22 -> 1.9.21

dropbox/differ:
0.0.1 -> 0.0.2

Desktop Compose Version

Compose Multiplatform:
1.4.3 -> 1.6.1

What's Changed

Full Changelog: takahirom/roborazzi@1.12.0...1.13.0

v1.12.0

Compare Source

Bug Fixes
  • Fixed an issue where recorded images with a transparent background and a scaling option (e.g., 0.5F) were always detected as changes. Thanks for reporting this, @​yongsuk44!
  • Addressed a bug related to robolectric.screenshot.hwrdr.native introduced in Robolectric 4.12, which caused unwanted shadows when using Compose's roboCaptureImage{} with this new option. This has now been corrected by @​lukas-mercari. Thanks for your contribution!
What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.11.0...1.12.0

v1.11.0

Compare Source

New feature

In Roborazzi, if you specify outputDir in the Gradle settings, you can use the build cache. Now, Roborazzi passes the setting into the test.

build.gradle

roborazzi {
    outputDir = "src/your/screenshot/folder"
}

gradle.propeties

roborazzi.record.filePathStrategy=relativePathFromRoborazziContextOutputDirectory

Test

captureRoboImage()
-> saved src/your/screenshot/folder/package.class.method.png

captureRoboImage("test.png")

-> saved src/your/screenshot/folder/test.png
What's Changed

Full Changelog: takahirom/roborazzi@1.10.1...1.11.0

v1.10.1

Compare Source

Changes from 1.10.0

This release includes a bug fix for a Javascript error that prevented the HTML report from being displayed.

Changes from 1.9.0
New experimental feature
Custom context data for images and reports

Custom context data enables the addition of information to images and reports in Roborazzi's tests, which I believe is very important. For example, it can include the test class name of a screenshot or whether it is in dark mode.
You can now add custom context data using RoborazziOptions, and Roborazzi will add the test class name metadata if you use RoborazziRule. If you have any opinions about this feature, please let me know at https://github.com/takahirom/roborazzi/issues/257.
Furthermore, this opens up possibilities with AI. Given that AI now possesses multimodal capabilities, it has become feasible for AI to process images.
This feature was made possible thanks to @​sanao1006 's contribution of migrating from org.json to gson.

    onView(ViewMatchers.isRoot())
      .captureRoboImage(
        roborazziOptions = RoborazziOptions(
          contextData = mapOf(
            "context_data_key" to "context_data_value"
          )
        )
      )
  }
image
Important bug fix

Gradle attempts to load the test cache whenever possible, but there was an issue where Roborazzi couldn't restore images from the cache. This release includes a fix for this problem. Thank you, @​francescocervone, for reporting this issue.

What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.9.0...1.10.0

v1.10.0

Compare Source

New experimental feature
Custom context data for images and reports

Custom context data enables the addition of information to images and reports in Roborazzi's tests, which I believe is very important. For example, it can include the test class name of a screenshot or whether it is in dark mode.
You can now add custom context data using RoborazziOptions, and Roborazzi will add the test class name metadata if you use RoborazziRule. If you have any opinions about this feature, please let me know at https://github.com/takahirom/roborazzi/issues/257.
Furthermore, this opens up possibilities with AI. Given that AI now possesses multimodal capabilities, it has become feasible for AI to process images.
This feature was made possible thanks to @​sanao1006 's contribution of migrating from org.json to gson.

    onView(ViewMatchers.isRoot())
      .captureRoboImage(
        roborazziOptions = RoborazziOptions(
          contextData = mapOf(
            "context_data_key" to "context_data_value"
          )
        )
      )
  }
image
Important bug fix

Gradle attempts to load the test cache whenever possible, but there was an issue where Roborazzi couldn't restore images from the cache. This release includes a fix for this problem. Thank you, @​francescocervone, for reporting this issue.

What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.9.0...1.10.0

v1.9.0

Compare Source

Announcement: Simplified Release Strategy for Roborazzi

We're making some changes to our release strategy to enhance your experience. Moving forward, we will be streamlining our versioning system. Instead of maintaining separate alpha/rc/stable versions, we will integrate experimental features directly into stable releases, marked with clear experimental annotations. This approach aims to simplify updates and improve clarity while ensuring you still have access to the latest features and improvements.

We value your input and experience. If you have any thoughts or feedback on this change, please feel free to share them with us on GitHub Issue #​243.

New Experimental Features

  • Introduction of captureScreenRoboImage() Function:
    This function executes screenshot tests that include dialogs on the screen, offering an alternative to the conventional use of Espresso's ViewInteraction or Compose Test's SemanticsNodeInteraction captureRoboImage(). Thank you, @​nelletto, for bringing this issue with dialog screenshots to our attention.

    Before:

    onRoot().captureRoboImage()
onView(isRoot()).captureRoboImage()

    After:

    captureScreenRoboImage()
image

  • RoborazziTaskType Property:
    I developed Roborazzi to facilitate layout viewing during UI tests, addressing the limitations in Robolectric's layout visibility. Initially, Roborazzi couldn't support just viewing layouts during the verification task (roborazziVerifyDebug). Hence, I've introduced a feature allowing task type alteration during test executions.

    onView(ViewMatchers.isRoot())
  .captureRoboImage(
    roborazziOptions = RoborazziOptions(
      taskType = roborazziSystemPropertyTaskType().convertVerifyingToComparing()
    )
  )
Behavior Changes
  • Adjustments for Upcoming Robolectric Shadow Rendering Support:
    While Robolectric is in the process of introducing technical support for shadow rendering, Roborazzi is adapting its screenshot capture method accordingly. We're shifting towards using the PixelCopy class more extensively instead of relying solely on the View draw method. If you notice any issues with this change, please report them to us. Thank you, @​sergio-sastre, for highlighting the advantages of using PixelCopy.
Bug Fixes
  • Fixed Potential Memory Leak:
    Addressed a memory leak issue occurring when using compose captureRoboImage{} multiple times within a single test. (Thanks for reporting this @​vetoketju )
  • Resolved File Path Duplication:
    Corrected an issue where not specifying a file path with relativePathFromRoborazziContextOutputDirectory resulted in duplicated file paths, like build/output/roborazzi/build/output/roborazzi/xxxx.png.
  • Fixed a bug in window ordering for screenshots: Windows are now accurately layered by type for more reliable and consistent screenshot results.
  • Fixed the issue where captureScreenRoboImage() failed to capture Material3 Compose dialogs and bottom sheets.
    @​marianeum Thank you for reporting this issue!
  • Resolved the issue causing comparison images to enlarge when using the scale option.
Others
What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.8.0...1.9.0

v1.8.0

Compare Source

Announcement: Simplified Release Strategy for Roborazzi

We're making some changes to our release strategy to enhance your experience. Moving forward, we will be streamlining our versioning system. Instead of maintaining separate alpha/rc/stable versions, we will integrate experimental features directly into stable releases, marked with clear experimental annotations. This approach aims to simplify updates and improve clarity while ensuring you still have access to the latest features and improvements.

We value your input and experience. If you have any thoughts or feedback on this change, please feel free to share them with us on GitHub Issue #​243.

Fix from 1.8.0-rc-1
New Feature from 1.7
Introducing the experimental roboOutputName() function

Streamline the customization of Roborazzi image file names. This utility is especially effective in parameterized tests, allowing for dynamic file naming based on test parameters. For an example of its usage, see the snippet below, which demonstrates generating screenshots before and after UI interactions.

@​Test
fun launchScreen() {
  // Generates a file named "org.your.pkg.TestClassName.launchScreen_before.png"
  onView(ViewMatchers.isRoot()).captureRoboImage("${roboOutputName()}_before.png")
  // Replace with specific actions, e.g., onView(xxx).performClick()
  
  // Generates a file named "org.your.pkg.TestClassName.launchScreen_after.png"
  onView(ViewMatchers.isRoot()).captureRoboImage("${roboOutputName()}_after.png")
}

Tailor your file naming convention in gradle.properties for even more control, such as omitting the package name.
Set roborazzi.record.namingStrategy=testClassAndMethod for a streamlined naming pattern.
Learn more: Roborazzi Documentation

Enhanced Comparison with Grid and Labels 🚀

This update introduces a new grid and label feature, making visual comparisons more intuitive and effective. The grid layout provides a structured view, while labels offer clear identification, streamlining the testing process.

You can use the old style by setting ComparisonStyle to ComparisonStyle.Simple in RoborazziOptions

  data class CompareOptions(
...
    val comparisonStyle: ComparisonStyle = ComparisonStyle.Grid(),
  ) {
    @​ExperimentalRoborazziApi
    sealed interface ComparisonStyle {
      @​ExperimentalRoborazziApi
      data class Grid(
        val bigLineSpaceDp: Int? = 16,
        val smallLineSpaceDp: Int? = 4,
        val hasLabel: Boolean = true
      ) : ComparisonStyle

      object Simple : ComparisonStyle
    }

image

Make Roborazzi's ImageComparator customizable.

You can now modify the ImageComparator using CompareOptions.imageComparator.

Behavior changes 🔧

Set the default value of CompareOptions.changeThreshold to zero. This means it will detect even a single pixel change.

What's Changed

Full Changelog: takahirom/roborazzi@1.7.0...1.8.0

v1.7.0

Compare Source

New Features 🚀
  • HTML Report
    You can now view the report, which includes images, when Roborazzi tasks are completed. The report is located at build/reports/roborazzi/index.html.
image
  • Added roborazzi.record.filePathStrategy option to customize image output location when using captureRoboImage(). The image will be saved relative to RoborazziRule's outputDirectoryPath. For example:
roborazzi.record.filePathStrategy=relativePathFromRoborazziContextOutputDirectory

image

Special thanks to @​timothyfroehlich for raising issues and providing valuable code reviews that significantly contributed to this release.

Breaking Changes ⚠️
  • To support the new HTML report feature, we've modified some options related to the existing JSON report. Previously, the JSON report was solely for the compare task, but it now covers all Roborazzi tasks. Therefore, we've updated the option names accordingly.
    Example: Change from ReportOptions.compareOptions.roborazziCompareReporter to RoborazziOptions.reportOptions.captureResultReporter, and update the corresponding reporter classes.
  • Renamed classes associated with CaptureResultReporter for consistency, which were introduced with version 1.7.0-alpha-1.
What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.6.0...1.7.0-rc-1

v1.6.0

Compare Source

Experimental feature: Compose Desktop support

Roborazzi supports Compose Desktop. You can use Roborazzi with Compose Desktop as follows:

Gradle settings

plugins {
  kotlin("multiplatform")
  id("org.jetbrains.compose")
  id("io.github.takahirom.roborazzi")
}

kotlin {
  // You can use your source set name
  jvm("desktop")
  sourceSets {
    ...
    val desktopTest by getting {
      dependencies {
        implementation(project("io.github.takahirom.roborazzi:roborazzi-compose-desktop:[1.6.0-alpha-2 or higher]"))
        implementation(kotlin("test"))
      }
    }
  ...

// Roborazzi Desktop support uses Context Receivers
tasks.withType<KotlinCompile>().configureEach {
  kotlinOptions {
    freeCompilerArgs += "-Xcontext-receivers"
  }
}

Test target Composable function

@&#8203;Composable
fun App() {
  var text by remember { mutableStateOf("Hello, World!") }

  MaterialTheme {
    Button(
      modifier = Modifier.testTag("button"),
      onClick = {
        text = "Hello, Desktop!"
      }) {
      Text(
        style = MaterialTheme.typography.h2,
        text = text
      )
    }
  }
}

Test with Roborazzi

class MainKmpTest {
  @&#8203;OptIn(ExperimentalTestApi::class)
  @&#8203;Test
  fun test() = runDesktopComposeUiTest {
    setContent {
      App()
    }
    val roborazziOptions = RoborazziOptions(
      recordOptions = RoborazziOptions.RecordOptions(
        resizeScale = 0.5
      ),
      compareOptions = RoborazziOptions.CompareOptions(
        changeThreshold = 0F
      )
    )
    onRoot().captureRoboImage(roborazziOptions = roborazziOptions)

    onNodeWithTag("button").performClick()

    onRoot().captureRoboImage(roborazziOptions = roborazziOptions)
  }
}

Then, you can run the Gradle tasks for Desktop Support, just like you do for Android Support.

./gradlew

Configuration

📅 Schedule: Branch creation - "before 4am" in timezone Asia/Seoul, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@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 changed the title chore(deps): update test.roborazzi to v1.9.0 chore(deps): update test.roborazzi to v1.10.0 Feb 18, 2024
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.10.0 chore(deps): update test.roborazzi to v1.10.1 Feb 18, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 278c20b to 2108714 Compare March 18, 2024 04:32
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.10.1 chore(deps): update test.roborazzi to v1.11.0 Mar 18, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 2108714 to ad32264 Compare April 12, 2024 00:46
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.11.0 chore(deps): update test.roborazzi to v1.12.0 Apr 12, 2024
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.12.0 chore(deps): update test.roborazzi Apr 20, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from ad32264 to e4b5d50 Compare April 20, 2024 04:32
@renovate renovate bot changed the title chore(deps): update test.roborazzi chore(deps): update test.roborazzi to v1.13.0 Apr 20, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch 2 times, most recently from 4c7df78 to ea11434 Compare May 4, 2024 08:19
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.13.0 chore(deps): update test.roborazzi to v1.14.0 May 4, 2024
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.14.0 chore(deps): update test.roborazzi May 7, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from ea11434 to e889edf Compare May 7, 2024 03:41
@renovate renovate bot changed the title chore(deps): update test.roborazzi chore(deps): update test.roborazzi to v1.15.0 May 7, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from e889edf to 124fa38 Compare May 17, 2024 05:27
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.15.0 chore(deps): update test.roborazzi to v1.16.0 May 17, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 124fa38 to 1eaf995 Compare May 17, 2024 19:18
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.16.0 chore(deps): update test.roborazzi to v1.16.1 May 17, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 1eaf995 to 9a4c4cb Compare May 24, 2024 03:32
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.16.1 chore(deps): update test.roborazzi to v1.17.0 May 24, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from 9a4c4cb to a11ba92 Compare May 25, 2024 06:50
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.17.0 chore(deps): update test.roborazzi to v1.18.0 May 25, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from a11ba92 to d531a23 Compare May 27, 2024 13:20
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.18.0 chore(deps): update test.roborazzi to v1.19.0 May 27, 2024
@renovate renovate bot changed the title chore(deps): update test.roborazzi to v1.19.0 chore(deps): update test.roborazzi May 29, 2024
@renovate renovate bot force-pushed the renovate/test.roborazzi branch from d531a23 to 5f0938b Compare May 29, 2024 04:36
@renovate renovate bot changed the title chore(deps): update test.roborazzi chore(deps): update test.roborazzi to v1.20.0 May 29, 2024
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.

None yet
0 participants