Bump roborazzi from 1.64.0 to 1.68.0

[dependabot]

Bumps roborazzi from 1.64.0 to 1.68.0.
Updates io.github.takahirom.roborazzi:roborazzi from 1.64.0 to 1.68.0

Release notes

Sourced from io.github.takahirom.roborazzi:roborazzi's releases.

1.68.0

Compose Testing v2 (ui-test-junit4 v2) support (experimental)

If you've upgraded to Compose 1.11.0, where the v2 testing APIs (androidx.compose.ui.test.junit4.v2) are the default and the v1 rules are deprecated, Roborazzi now works with the v2 rule factories out of the box — createAndroidComposeRule from either package just works with RoborazziRule, captureRoboImage, and generated preview tests.

If you have a custom ComposePreviewTester, you can also delete the unchecked cast that used to be required:

override fun options(): ComposePreviewTester.Options = super.options().copy(
  testLifecycleOptions = ComposePreviewTester.Options.JUnit4TestLifecycleOptions(
    composeRuleFactory = {
      // v1 or v2 createAndroidComposeRule both work; no cast needed anymore
      createAndroidComposeRule<RoborazziActivity>()
    },
    ...
  )
)

What you might need to change

Most users need no changes. The exception: the options APIs now accept the ComposeTestRule / ComposeContentTestRule interfaces instead of the concrete AndroidComposeTestRule<...> type, so composeTestRule.activityRule is no longer reachable through them. Roborazzi finds your rule's activity automatically; if it can't, it fails loudly (instead of silently capturing the wrong activity) and tells you to pass the scenario yourself:

• composeTestRule(rule) { activityScenario } for direct capture calls
• JUnit4TestLifecycleOptions.activityScenarioProvider for generated preview tests

The new sample-compose-v2 module shows both, running against stable Compose 1.11.0.

Compatibility

Libraries compiled against 1.67.0 keep working — the old entry points are preserved as hidden binary-compat bridges. If you compile against 1.68.0, typical code compiles as-is (or gets simpler, as above). Known remaining binary-level changes on these @ExperimentalRoborazziApi surfaces: JUnit4TestParameter.getComposeTestRule's return type and the data-class copy signatures of JUnit4TestLifecycleOptions / RoborazziComposeTestRuleOption; recompiling resolves them.

@PreviewWrapper previews now appear correctly in screenshots

If you use Compose UI 1.11's @PreviewWrapper to wrap previews in a theme or background, those wrappers now show up in your Roborazzi preview screenshots with no extra setup — just use ComposablePreviewScanner 0.9.0 or later (#823):

class DarkThemeWrapperProvider : PreviewWrapperProvider {
  @Composable
  override fun Wrap(content: @Composable () -> Unit) {
    MaterialTheme(colorScheme = darkColorScheme()) { content() }
  }
}
@​PreviewWrapper(DarkThemeWrapperProvider::class)
@​Preview
@​Composable
fun WrappedPreview() { ... }

... (truncated)

Commits

• a8f9c76 1.68.0
• f11bc23 Merge pull request #874 from takahirom/tm/add-preview-wrapper-sample
• 0349fcf Suppress deprecation warnings for scanner common module in sample
• 8e6753e Add Compose PreviewWrapper sample preview test
• 1a45b27 Merge pull request #873 from takahirom/tm/junit4-lifecycle-options-binary-compat
• e6b9357 Restore 1.67.0 binary-compat constructors for JUnit4TestLifecycleOptions
• 70c84b0 Merge pull request #816 from takahirom/tm/abstract-compose-test-rule-for-v2-s...
• 0ebd4b5 Merge branch 'main' into tm/abstract-compose-test-rule-for-v2-support
• a779353 Merge pull request #872 from takahirom/tm/fix-flaky-desktop-screenshot
• 19cf44d Fix flaky desktop screenshot diffs by pinning runner and threshold
• Additional commits viewable in compare view

Updates io.github.takahirom.roborazzi:roborazzi-compose from 1.64.0 to 1.68.0

Release notes

Sourced from io.github.takahirom.roborazzi:roborazzi-compose's releases.

1.68.0

Compose Testing v2 (ui-test-junit4 v2) support (experimental)

If you've upgraded to Compose 1.11.0, where the v2 testing APIs (androidx.compose.ui.test.junit4.v2) are the default and the v1 rules are deprecated, Roborazzi now works with the v2 rule factories out of the box — createAndroidComposeRule from either package just works with RoborazziRule, captureRoboImage, and generated preview tests.

If you have a custom ComposePreviewTester, you can also delete the unchecked cast that used to be required:

override fun options(): ComposePreviewTester.Options = super.options().copy(
  testLifecycleOptions = ComposePreviewTester.Options.JUnit4TestLifecycleOptions(
    composeRuleFactory = {
      // v1 or v2 createAndroidComposeRule both work; no cast needed anymore
      createAndroidComposeRule<RoborazziActivity>()
    },
    ...
  )
)

What you might need to change

Most users need no changes. The exception: the options APIs now accept the ComposeTestRule / ComposeContentTestRule interfaces instead of the concrete AndroidComposeTestRule<...> type, so composeTestRule.activityRule is no longer reachable through them. Roborazzi finds your rule's activity automatically; if it can't, it fails loudly (instead of silently capturing the wrong activity) and tells you to pass the scenario yourself:

• composeTestRule(rule) { activityScenario } for direct capture calls
• JUnit4TestLifecycleOptions.activityScenarioProvider for generated preview tests

The new sample-compose-v2 module shows both, running against stable Compose 1.11.0.

Compatibility

Libraries compiled against 1.67.0 keep working — the old entry points are preserved as hidden binary-compat bridges. If you compile against 1.68.0, typical code compiles as-is (or gets simpler, as above). Known remaining binary-level changes on these @ExperimentalRoborazziApi surfaces: JUnit4TestParameter.getComposeTestRule's return type and the data-class copy signatures of JUnit4TestLifecycleOptions / RoborazziComposeTestRuleOption; recompiling resolves them.

@PreviewWrapper previews now appear correctly in screenshots

If you use Compose UI 1.11's @PreviewWrapper to wrap previews in a theme or background, those wrappers now show up in your Roborazzi preview screenshots with no extra setup — just use ComposablePreviewScanner 0.9.0 or later (#823):

class DarkThemeWrapperProvider : PreviewWrapperProvider {
  @Composable
  override fun Wrap(content: @Composable () -> Unit) {
    MaterialTheme(colorScheme = darkColorScheme()) { content() }
  }
}
@​PreviewWrapper(DarkThemeWrapperProvider::class)
@​Preview
@​Composable
fun WrappedPreview() { ... }

... (truncated)

Commits

• a8f9c76 1.68.0
• f11bc23 Merge pull request #874 from takahirom/tm/add-preview-wrapper-sample
• 0349fcf Suppress deprecation warnings for scanner common module in sample
• 8e6753e Add Compose PreviewWrapper sample preview test
• 1a45b27 Merge pull request #873 from takahirom/tm/junit4-lifecycle-options-binary-compat
• e6b9357 Restore 1.67.0 binary-compat constructors for JUnit4TestLifecycleOptions
• 70c84b0 Merge pull request #816 from takahirom/tm/abstract-compose-test-rule-for-v2-s...
• 0ebd4b5 Merge branch 'main' into tm/abstract-compose-test-rule-for-v2-support
• a779353 Merge pull request #872 from takahirom/tm/fix-flaky-desktop-screenshot
• 19cf44d Fix flaky desktop screenshot diffs by pinning runner and threshold
• Additional commits viewable in compare view

Updates io.github.takahirom.roborazzi:roborazzi-junit-rule from 1.64.0 to 1.68.0

Release notes

Sourced from io.github.takahirom.roborazzi:roborazzi-junit-rule's releases.

1.68.0

Compose Testing v2 (ui-test-junit4 v2) support (experimental)

If you've upgraded to Compose 1.11.0, where the v2 testing APIs (androidx.compose.ui.test.junit4.v2) are the default and the v1 rules are deprecated, Roborazzi now works with the v2 rule factories out of the box — createAndroidComposeRule from either package just works with RoborazziRule, captureRoboImage, and generated preview tests.

If you have a custom ComposePreviewTester, you can also delete the unchecked cast that used to be required:

override fun options(): ComposePreviewTester.Options = super.options().copy(
  testLifecycleOptions = ComposePreviewTester.Options.JUnit4TestLifecycleOptions(
    composeRuleFactory = {
      // v1 or v2 createAndroidComposeRule both work; no cast needed anymore
      createAndroidComposeRule<RoborazziActivity>()
    },
    ...
  )
)

What you might need to change

Most users need no changes. The exception: the options APIs now accept the ComposeTestRule / ComposeContentTestRule interfaces instead of the concrete AndroidComposeTestRule<...> type, so composeTestRule.activityRule is no longer reachable through them. Roborazzi finds your rule's activity automatically; if it can't, it fails loudly (instead of silently capturing the wrong activity) and tells you to pass the scenario yourself:

• composeTestRule(rule) { activityScenario } for direct capture calls
• JUnit4TestLifecycleOptions.activityScenarioProvider for generated preview tests

The new sample-compose-v2 module shows both, running against stable Compose 1.11.0.

Compatibility

Libraries compiled against 1.67.0 keep working — the old entry points are preserved as hidden binary-compat bridges. If you compile against 1.68.0, typical code compiles as-is (or gets simpler, as above). Known remaining binary-level changes on these @ExperimentalRoborazziApi surfaces: JUnit4TestParameter.getComposeTestRule's return type and the data-class copy signatures of JUnit4TestLifecycleOptions / RoborazziComposeTestRuleOption; recompiling resolves them.

@PreviewWrapper previews now appear correctly in screenshots

If you use Compose UI 1.11's @PreviewWrapper to wrap previews in a theme or background, those wrappers now show up in your Roborazzi preview screenshots with no extra setup — just use ComposablePreviewScanner 0.9.0 or later (#823):

class DarkThemeWrapperProvider : PreviewWrapperProvider {
  @Composable
  override fun Wrap(content: @Composable () -> Unit) {
    MaterialTheme(colorScheme = darkColorScheme()) { content() }
  }
}
@​PreviewWrapper(DarkThemeWrapperProvider::class)
@​Preview
@​Composable
fun WrappedPreview() { ... }

... (truncated)

Commits

• a8f9c76 1.68.0
• f11bc23 Merge pull request #874 from takahirom/tm/add-preview-wrapper-sample
• 0349fcf Suppress deprecation warnings for scanner common module in sample
• 8e6753e Add Compose PreviewWrapper sample preview test
• 1a45b27 Merge pull request #873 from takahirom/tm/junit4-lifecycle-options-binary-compat
• e6b9357 Restore 1.67.0 binary-compat constructors for JUnit4TestLifecycleOptions
• 70c84b0 Merge pull request #816 from takahirom/tm/abstract-compose-test-rule-for-v2-s...
• 0ebd4b5 Merge branch 'main' into tm/abstract-compose-test-rule-for-v2-support
• a779353 Merge pull request #872 from takahirom/tm/fix-flaky-desktop-screenshot
• 19cf44d Fix flaky desktop screenshot diffs by pinning runner and threshold
• Additional commits viewable in compare view

Updates io.github.takahirom.roborazzi from 1.64.0 to 1.68.0

Release notes

Sourced from io.github.takahirom.roborazzi's releases.

1.68.0

Compose Testing v2 (ui-test-junit4 v2) support (experimental)

If you've upgraded to Compose 1.11.0, where the v2 testing APIs (androidx.compose.ui.test.junit4.v2) are the default and the v1 rules are deprecated, Roborazzi now works with the v2 rule factories out of the box — createAndroidComposeRule from either package just works with RoborazziRule, captureRoboImage, and generated preview tests.

If you have a custom ComposePreviewTester, you can also delete the unchecked cast that used to be required:

override fun options(): ComposePreviewTester.Options = super.options().copy(
  testLifecycleOptions = ComposePreviewTester.Options.JUnit4TestLifecycleOptions(
    composeRuleFactory = {
      // v1 or v2 createAndroidComposeRule both work; no cast needed anymore
      createAndroidComposeRule<RoborazziActivity>()
    },
    ...
  )
)

What you might need to change

Most users need no changes. The exception: the options APIs now accept the ComposeTestRule / ComposeContentTestRule interfaces instead of the concrete AndroidComposeTestRule<...> type, so composeTestRule.activityRule is no longer reachable through them. Roborazzi finds your rule's activity automatically; if it can't, it fails loudly (instead of silently capturing the wrong activity) and tells you to pass the scenario yourself:

• composeTestRule(rule) { activityScenario } for direct capture calls
• JUnit4TestLifecycleOptions.activityScenarioProvider for generated preview tests

The new sample-compose-v2 module shows both, running against stable Compose 1.11.0.

Compatibility

Libraries compiled against 1.67.0 keep working — the old entry points are preserved as hidden binary-compat bridges. If you compile against 1.68.0, typical code compiles as-is (or gets simpler, as above). Known remaining binary-level changes on these @ExperimentalRoborazziApi surfaces: JUnit4TestParameter.getComposeTestRule's return type and the data-class copy signatures of JUnit4TestLifecycleOptions / RoborazziComposeTestRuleOption; recompiling resolves them.

@PreviewWrapper previews now appear correctly in screenshots

If you use Compose UI 1.11's @PreviewWrapper to wrap previews in a theme or background, those wrappers now show up in your Roborazzi preview screenshots with no extra setup — just use ComposablePreviewScanner 0.9.0 or later (#823):

class DarkThemeWrapperProvider : PreviewWrapperProvider {
  @Composable
  override fun Wrap(content: @Composable () -> Unit) {
    MaterialTheme(colorScheme = darkColorScheme()) { content() }
  }
}
@​PreviewWrapper(DarkThemeWrapperProvider::class)
@​Preview
@​Composable
fun WrappedPreview() { ... }

... (truncated)

Commits

• a8f9c76 1.68.0
• f11bc23 Merge pull request #874 from takahirom/tm/add-preview-wrapper-sample
• 0349fcf Suppress deprecation warnings for scanner common module in sample
• 8e6753e Add Compose PreviewWrapper sample preview test
• 1a45b27 Merge pull request #873 from takahirom/tm/junit4-lifecycle-options-binary-compat
• e6b9357 Restore 1.67.0 binary-compat constructors for JUnit4TestLifecycleOptions
• 70c84b0 Merge pull request #816 from takahirom/tm/abstract-compose-test-rule-for-v2-s...
• 0ebd4b5 Merge branch 'main' into tm/abstract-compose-test-rule-for-v2-support
• a779353 Merge pull request #872 from takahirom/tm/fix-flaky-desktop-screenshot
• 19cf44d Fix flaky desktop screenshot diffs by pinning runner and threshold
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)