Skip to content

build(deps): bump the test-tooling group across 1 directory with 4 updates - #188

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/gradle/master/test-tooling-defd01cac3
Open

build(deps): bump the test-tooling group across 1 directory with 4 updates#188
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/gradle/master/test-tooling-defd01cac3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the test-tooling group with 4 updates in the / directory: org.robolectric:robolectric, io.github.takahirom.roborazzi:roborazzi-compose, io.github.takahirom.roborazzi:roborazzi and io.github.takahirom.roborazzi.

Updates org.robolectric:robolectric from 4.16.1 to 4.17

Release notes

Sourced from org.robolectric:robolectric's releases.

Robolectric 4.17 supports SDK 37 and contains many other features and enhancements.

Please note you may need to add jvmFlags configuration when using JDKs >= 17 at https://robolectric.org/getting-started/

If you have any issues, please file them here.

Breaking Changes

AndroidVersions has been removed in favor of using android.os.Build constants ShadowCameraCharacteristics.set(Key, Object) has been changed to set(Key, T), in order to correctly reflect type enforcement in the framework

What's Changed

... (truncated)

Commits
  • 0706415 Bump version to 4.17.
  • f3c17bd Bump version to 4.17-beta-4.
  • 04b84f6 "fixed ResTable_package.SIZEOF value
  • f4ee543 Apply suggestion from @​gemini-code-assist[bot]
  • fb99bfb Expose BouncyCastle BoM as api dependency
  • a453192 Fix Javadoc for VersionCalculator
  • 6f26892 Bump version to 4.17-beta-3
  • ceffe96 Only adjust frameinfo timestamp values (including vsync).
  • ea5879f Add opt-in fix for stale screenshots on SDK 37.
  • 8bea421 Fix jank log spam on SDK 37+ by translating FrameInfo timestamps.
  • Additional commits viewable in compare view

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

Release notes

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

1.74.0

Fixes

  • A popup opened from inside a dialog was drawn at the wrong position. captureScreenRoboImage() composites every window onto one canvas, and it placed all of them against the screen. That is right for an Activity or a Dialog, whose layout params x/y are screen relative, but a sub-window — a PopupWindow, a Spinner drop-down, a Compose Popup/DropdownMenu — stores x/y relative to the window its anchor lives in. For an anchor in an Activity that window sits at the screen origin, so the two agree and nobody noticed; for an anchor inside a Dialog the popup was offset by the dialog's own position. Sub-windows are now placed against their parent window, found through the application window token their layout params carry. A window that laid itself out in screen coordinates (FLAG_LAYOUT_IN_SCREEN, e.g. PopupWindow.setIsLaidOutInScreen(true)) keeps its coordinates, and an unresolvable parent falls back to the previous screen-relative behavior (#922, fixes #921). Thank you @​david-allison for the report with a reproducer commit in AnkiDroid!

What's Changed

Full Changelog: takahirom/roborazzi@1.73.0...1.74.0

1.73.0

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

1.72.0

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!

... (truncated)

Commits
  • 56f6987 1.74.0
  • e30f61a Fix popup window position when its parent window is a dialog (#922)
  • 6abd5fc 1.73.0
  • 9197a9f Register generated preview tests input with relative path sensitivity (#919)
  • c6537f8 Skip the pixel comparison when images are already identical (#917)
  • 92249fb 1.72.0
  • cf5a975 Merge pull request #916 from takahirom/tm/915-windows-output-path
  • 7b6b88a Merge pull request #909 from takahirom/tm/subdirectory-naming-strategy
  • 9e81573 Harden compare subtree mirroring test state restoration and assertions
  • 76c7fbe Use rule override output directory for compare subtree mirroring
  • Additional commits viewable in compare view

Updates io.github.takahirom.roborazzi:roborazzi from 1.68.0 to 1.74.0

Release notes

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

1.74.0

Fixes

  • A popup opened from inside a dialog was drawn at the wrong position. captureScreenRoboImage() composites every window onto one canvas, and it placed all of them against the screen. That is right for an Activity or a Dialog, whose layout params x/y are screen relative, but a sub-window — a PopupWindow, a Spinner drop-down, a Compose Popup/DropdownMenu — stores x/y relative to the window its anchor lives in. For an anchor in an Activity that window sits at the screen origin, so the two agree and nobody noticed; for an anchor inside a Dialog the popup was offset by the dialog's own position. Sub-windows are now placed against their parent window, found through the application window token their layout params carry. A window that laid itself out in screen coordinates (FLAG_LAYOUT_IN_SCREEN, e.g. PopupWindow.setIsLaidOutInScreen(true)) keeps its coordinates, and an unresolvable parent falls back to the previous screen-relative behavior (#922, fixes #921). Thank you @​david-allison for the report with a reproducer commit in AnkiDroid!

What's Changed

Full Changelog: takahirom/roborazzi@1.73.0...1.74.0

1.73.0

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

1.72.0

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!

... (truncated)

Commits
  • 56f6987 1.74.0
  • e30f61a Fix popup window position when its parent window is a dialog (#922)
  • 6abd5fc 1.73.0
  • 9197a9f Register generated preview tests input with relative path sensitivity (#919)
  • c6537f8 Skip the pixel comparison when images are already identical (#917)
  • 92249fb 1.72.0
  • cf5a975 Merge pull request #916 from takahirom/tm/915-windows-output-path
  • 7b6b88a Merge pull request #909 from takahirom/tm/subdirectory-naming-strategy
  • 9e81573 Harden compare subtree mirroring test state restoration and assertions
  • 76c7fbe Use rule override output directory for compare subtree mirroring
  • Additional commits viewable in compare view

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

Release notes

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

1.74.0

Fixes

  • A popup opened from inside a dialog was drawn at the wrong position. captureScreenRoboImage() composites every window onto one canvas, and it placed all of them against the screen. That is right for an Activity or a Dialog, whose layout params x/y are screen relative, but a sub-window — a PopupWindow, a Spinner drop-down, a Compose Popup/DropdownMenu — stores x/y relative to the window its anchor lives in. For an anchor in an Activity that window sits at the screen origin, so the two agree and nobody noticed; for an anchor inside a Dialog the popup was offset by the dialog's own position. Sub-windows are now placed against their parent window, found through the application window token their layout params carry. A window that laid itself out in screen coordinates (FLAG_LAYOUT_IN_SCREEN, e.g. PopupWindow.setIsLaidOutInScreen(true)) keeps its coordinates, and an unresolvable parent falls back to the previous screen-relative behavior (#922, fixes #921). Thank you @​david-allison for the report with a reproducer commit in AnkiDroid!

What's Changed

Full Changelog: takahirom/roborazzi@1.73.0...1.74.0

1.73.0

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

1.72.0

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!

... (truncated)

Commits
  • 56f6987 1.74.0
  • e30f61a Fix popup window position when its parent window is a dialog (#922)
  • 6abd5fc 1.73.0
  • 9197a9f Register generated preview tests input with relative path sensitivity (#919)
  • c6537f8 Skip the pixel comparison when images are already identical (#917)
  • 92249fb 1.72.0
  • cf5a975 Merge pull request #916 from takahirom/tm/915-windows-output-path
  • 7b6b88a Merge pull request #909 from takahirom/tm/subdirectory-naming-strategy
  • 9e81573 Harden compare subtree mirroring test state restoration and assertions
  • 76c7fbe Use rule override output directory for compare subtree mirroring
  • Additional commits viewable in compare view

Updates io.github.takahirom.roborazzi:roborazzi from 1.68.0 to 1.74.0

Release notes

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

1.74.0

Fixes

  • A popup opened from inside a dialog was drawn at the wrong position. captureScreenRoboImage() composites every window onto one canvas, and it placed all of them against the screen. That is right for an Activity or a Dialog, whose layout params x/y are screen relative, but a sub-window — a PopupWindow, a Spinner drop-down, a Compose Popup/DropdownMenu — stores x/y relative to the window its anchor lives in. For an anchor in an Activity that window sits at the screen origin, so the two agree and nobody noticed; for an anchor inside a Dialog the popup was offset by the dialog's own position. Sub-windows are now placed against their parent window, found through the application window token their layout params carry. A window that laid itself out in screen coordinates (FLAG_LAYOUT_IN_SCREEN, e.g. PopupWindow.setIsLaidOutInScreen(true)) keeps its coordinates, and an unresolvable parent falls back to the previous screen-relative behavior (#922, fixes #921). Thank you @​david-allison for the report with a reproducer commit in AnkiDroid!

What's Changed

Full Changelog: takahirom/roborazzi@1.73.0...1.74.0

1.73.0

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

1.72.0

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!

... (truncated)

Commits
  • 56f6987 1.74.0
  • e30f61a Fix popup window position when its parent window is a dialog (#922)
  • 6abd5fc 1.73.0
  • 9197a9f Register generated preview tests input with relative path sensitivity (#919)
  • c6537f8 Skip the pixel comparison when images are already identical (#917)
  • 92249fb 1.72.0
  • cf5a975 Merge pull request #916 from takahirom/tm/915-windows-output-path
  • 7b6b88a Merge pull request #909 from takahirom/tm/subdirectory-naming-strategy
  • 9e81573 Harden compare subtree mirroring test state restoration and assertions
  • 76c7fbe Use rule override output directory for compare subtree mirroring
  • Additional commits viewable in compare view

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

Release notes

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

1.74.0

Fixes

  • A popup opened from inside a dialog was drawn at the wrong position. captureScreenRoboImage() composites every window onto one canvas, and it placed all of them against the screen. That is right for an Activity or a Dialog, whose layout params x/y are screen relative, but a sub-window — a PopupWindow, a Spinner drop-down, a Compose Popup/DropdownMenu — stores x/y relative to the window its anchor lives in. For an anchor in an Activity that window sits at the screen origin, so the two agree and nobody noticed; for an anchor inside a Dialog the popup was offset by the dialog's own position. Sub-windows are now placed against their parent window, found through the application window token their layout params carry. A window that laid itself out in screen coordinates (FLAG_LAYOUT_IN_SCREEN, e.g. PopupWindow.setIsLaidOutInScreen(true)) keeps its coordinates, and an unresolvable parent falls back to the previous screen-relative behavior (#922, fixes #921). Thank you @​david-allison for the report with a reproducer commit in AnkiDroid!

What's Changed

Full Changelog: takahirom/roborazzi@1.73.0...1.74.0

1.73.0

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

1.72.0

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!

... (truncated)

Commits
  • 56f6987 1.74.0
  • e30f61a Fix popup window position when its parent window is a dialog (#922)
  • 6abd5fc 1.73.0
  • 9197a9f Register generated preview tests input with relative path sensitivity (#919)
  • c6537f8 Skip the pixel comparison when images are already identical (#917)
  • 92249fb 1.72.0
  • cf5a975 Merge pull request #916 from takahirom/tm/915-windows-output-path
  • 7b6b88a Merge pull request #909 from takahirom/tm/subdirectory-naming-strategy
  • 9e81573 Harden compare subtree mirroring test state restoration and assertions
  • 76c7fbe Use rule override output directory for compare subtree mirroring
  • 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
build(deps): bump the test-tooling group across 1 directory with 4 up…
dae988e 
…dates

Bumps the test-tooling group with 4 updates in the / directory: [org.robolectric:robolectric](https://github.com/robolectric/robolectric), [io.github.takahirom.roborazzi:roborazzi-compose](https://github.com/takahirom/roborazzi), [io.github.takahirom.roborazzi:roborazzi](https://github.com/takahirom/roborazzi) and [io.github.takahirom.roborazzi](https://github.com/takahirom/roborazzi).


Updates `org.robolectric:robolectric` from 4.16.1 to 4.17
- [Release notes](https://github.com/robolectric/robolectric/releases)
- [Commits](robolectric/robolectric@robolectric-4.16.1...robolectric-4.17)

Updates `io.github.takahirom.roborazzi:roborazzi-compose` from 1.68.0 to 1.74.0
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](takahirom/roborazzi@1.68.0...1.74.0)

Updates `io.github.takahirom.roborazzi:roborazzi` from 1.68.0 to 1.74.0
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](takahirom/roborazzi@1.68.0...1.74.0)

Updates `io.github.takahirom.roborazzi` from 1.68.0 to 1.74.0
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](takahirom/roborazzi@1.68.0...1.74.0)

Updates `io.github.takahirom.roborazzi:roborazzi` from 1.68.0 to 1.74.0
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](takahirom/roborazzi@1.68.0...1.74.0)

Updates `io.github.takahirom.roborazzi` from 1.68.0 to 1.74.0
- [Release notes](https://github.com/takahirom/roborazzi/releases)
- [Commits](takahirom/roborazzi@1.68.0...1.74.0)

---
updated-dependencies:
- dependency-name: org.robolectric:robolectric
  dependency-version: '4.17'
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: test-tooling
- dependency-name: io.github.takahirom.roborazzi:roborazzi-compose
  dependency-version: 1.74.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: test-tooling
- dependency-name: io.github.takahirom.roborazzi:roborazzi
  dependency-version: 1.74.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: test-tooling
- dependency-name: io.github.takahirom.roborazzi
  dependency-version: 1.74.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: test-tooling
- dependency-name: io.github.takahirom.roborazzi:roborazzi
  dependency-version: 1.74.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: test-tooling
- dependency-name: io.github.takahirom.roborazzi
  dependency-version: 1.74.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: test-tooling
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Sep 14, 2026

This branch has not been deployed

No deployments
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 Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants