chore(deps)(deps): bump the testing group with 4 updates

[dependabot]

Bumps the testing group with 4 updates: io.github.takahirom.roborazzi:roborazzi, io.github.takahirom.roborazzi:roborazzi-compose, io.github.takahirom.roborazzi:roborazzi-junit-rule and io.github.takahirom.roborazzi.

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

Release notes

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

1.69.0

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE] The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root":
 { "type": "compose", "bounds": [0, 0, 880, 748], "children": [
  { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] }
}

The annotated image draws each numbered node onto the screenshot — the numbers are exactly the n values in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.

Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.

Details:

... (truncated)

Commits

• 42b00b5 1.69.0
• e74d48f Merge pull request #886 from takahirom/takahirom/fix-webp-overwrite-truncation
• 241010a Merge pull request #884 from takahirom/tm/uitree-5-release-hardening
• 25251c7 Use assertTrue and assertThrows in annotation hardening test
• ed31f42 Use assertTrue instead of assert in ImageIoFormatOverwriteTest
• 4c602dc Merge pull request #885 from takahirom/tm/optimize-bitmap-to-bufferedimage
• acd9bff Fix WebP golden file corruption when overwriting with a smaller image
• 9dc8c79 Clean up shared outputs in boxed UI tree tests
• 962cb7e Name annotation-writer lambdas in desktop and iOS dump helpers
• 0e22bf3 Signal actual-image writes explicitly to annotated image writer
• Additional commits viewable in compare view

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

Release notes

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

1.69.0

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE] The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root":
 { "type": "compose", "bounds": [0, 0, 880, 748], "children": [
  { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] }
}

The annotated image draws each numbered node onto the screenshot — the numbers are exactly the n values in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.

Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.

Details:

... (truncated)

Commits

• 42b00b5 1.69.0
• e74d48f Merge pull request #886 from takahirom/takahirom/fix-webp-overwrite-truncation
• 241010a Merge pull request #884 from takahirom/tm/uitree-5-release-hardening
• 25251c7 Use assertTrue and assertThrows in annotation hardening test
• ed31f42 Use assertTrue instead of assert in ImageIoFormatOverwriteTest
• 4c602dc Merge pull request #885 from takahirom/tm/optimize-bitmap-to-bufferedimage
• acd9bff Fix WebP golden file corruption when overwriting with a smaller image
• 9dc8c79 Clean up shared outputs in boxed UI tree tests
• 962cb7e Name annotation-writer lambdas in desktop and iOS dump helpers
• 0e22bf3 Signal actual-image writes explicitly to annotated image writer
• Additional commits viewable in compare view

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

Release notes

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

1.69.0

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE] The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root":
 { "type": "compose", "bounds": [0, 0, 880, 748], "children": [
  { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] }
}

The annotated image draws each numbered node onto the screenshot — the numbers are exactly the n values in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.

Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.

Details:

... (truncated)

Commits

• 42b00b5 1.69.0
• e74d48f Merge pull request #886 from takahirom/takahirom/fix-webp-overwrite-truncation
• 241010a Merge pull request #884 from takahirom/tm/uitree-5-release-hardening
• 25251c7 Use assertTrue and assertThrows in annotation hardening test
• ed31f42 Use assertTrue instead of assert in ImageIoFormatOverwriteTest
• 4c602dc Merge pull request #885 from takahirom/tm/optimize-bitmap-to-bufferedimage
• acd9bff Fix WebP golden file corruption when overwriting with a smaller image
• 9dc8c79 Clean up shared outputs in boxed UI tree tests
• 962cb7e Name annotation-writer lambdas in desktop and iOS dump helpers
• 0e22bf3 Signal actual-image writes explicitly to annotated image writer
• Additional commits viewable in compare view

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

Release notes

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

1.69.0

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE] The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root":
 { "type": "compose", "bounds": [0, 0, 880, 748], "children": [
  { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] }
}

The annotated image draws each numbered node onto the screenshot — the numbers are exactly the n values in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.

Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.

Details:

... (truncated)

Commits

• 42b00b5 1.69.0
• e74d48f Merge pull request #886 from takahirom/takahirom/fix-webp-overwrite-truncation
• 241010a Merge pull request #884 from takahirom/tm/uitree-5-release-hardening
• 25251c7 Use assertTrue and assertThrows in annotation hardening test
• ed31f42 Use assertTrue instead of assert in ImageIoFormatOverwriteTest
• 4c602dc Merge pull request #885 from takahirom/tm/optimize-bitmap-to-bufferedimage
• acd9bff Fix WebP golden file corruption when overwriting with a smaller image
• 9dc8c79 Clean up shared outputs in boxed UI tree tests
• 962cb7e Name annotation-writer lambdas in desktop and iOS dump helpers
• 0e22bf3 Signal actual-image writes explicitly to annotated image writer
• Additional commits viewable in compare view

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

Release notes

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

1.69.0

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE] The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root":
 { "type": "compose", "bounds": [0, 0, 880, 748], "children": [
  { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] }
}

The annotated image draws each numbered node onto the screenshot — the numbers are exactly the n values in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.

Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.

Details:

... (truncated)

Commits

• 42b00b5 1.69.0
• e74d48f Merge pull request #886 from takahirom/takahirom/fix-webp-overwrite-truncation
• 241010a Merge pull request #884 from takahirom/tm/uitree-5-release-hardening
• 25251c7 Use assertTrue and assertThrows in annotation hardening test
• ed31f42 Use assertTrue instead of assert in ImageIoFormatOverwriteTest
• 4c602dc Merge pull request #885 from takahirom/tm/optimize-bitmap-to-bufferedimage
• acd9bff Fix WebP golden file corruption when overwriting with a smaller image
• 9dc8c79 Clean up shared outputs in boxed UI tree tests
• 962cb7e Name annotation-writer lambdas in desktop and iOS dump helpers
• 0e22bf3 Signal actual-image writes explicitly to annotated image writer
• Additional commits viewable in compare view

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

Release notes

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

1.69.0

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE] The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root":
 { "type": "compose", "bounds": [0, 0, 880, 748], "children": [
  { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] }
}

The annotated image draws each numbered node onto the screenshot — the numbers are exactly the n values in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.

Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.

Details:

... (truncated)

Commits

• 42b00b5 1.69.0
• e74d48f Merge pull request #886 from takahirom/takahirom/fix-webp-overwrite-truncation
• 241010a Merge pull request #884 from takahirom/tm/uitree-5-release-hardening
• 25251c7 Use assertTrue and assertThrows in annotation hardening test
• ed31f42 Use assertTrue instead of assert in ImageIoFormatOverwriteTest
• 4c602dc Merge pull request #885 from takahirom/tm/optimize-bitmap-to-bufferedimage
• acd9bff Fix WebP golden file corruption when overwriting with a smaller image
• 9dc8c79 Clean up shared outputs in boxed UI tree tests
• 962cb7e Name annotation-writer lambdas in desktop and iOS dump helpers
• 0e22bf3 Signal actual-image writes explicitly to annotated image writer
• Additional commits viewable in compare view

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

Release notes

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

1.69.0

Performance: faster screenshot capture on the JVM

Every screenshot capture converts an Android Bitmap into an AWT BufferedImage. This conversion now writes pixels directly into the image's backing int array instead of going through a per-pixel setRGB pass plus an extra drawImage copy (#885). Recorded output is pixel-identical — verified by the CI baseline comparison across all sample screenshots.

UI tree dump for AI agents (experimental)

[!NOTE] The UI tree dump is experimental — if you try it with your AI setup, we'd love to hear what works and what's missing in the issues.

Roborazzi can now write a machine-readable description of your UI alongside every screenshot, designed for AI-agent workflows (#878, #879, #880, #883, #884). Enable it with a single Gradle property — no code changes:

./gradlew recordRoborazziDebug -Proborazzi.dumpUiTree=true

Each capture then produces three files:

MyTest.png            # the screenshot, as always
MyTest.uitree.json    # the UI tree: Compose semantics + View hierarchy
MyTest.annotated.png  # the screenshot with numbered boxes (Set-of-Mark)

MyTest.uitree.json is a grep-first JSON: one node per line carrying all of its attributes, so a single grep login_button returns the node's type, bounds, properties, and actions — while staying valid JSON for jq:

{ "schemaVersion": 1, "capture": { "imageWidth": 880, "imageHeight": 748, "scale": 1.0 }, "root":
 { "type": "compose", "bounds": [0, 0, 880, 748], "children": [
  { "n": 3, "type": "compose", "testTag": "login_button", "bounds": [66, 308, 814, 418], "properties": { "Role": "Button", "Text": "[Log in]" }, "actions": ["OnClick"], "flags": ["MergeDescendants"] } ] }
}

The annotated image draws each numbered node onto the screenshot — the numbers are exactly the n values in the JSON, so an AI agent (or a teammate) can say "element #3" and look up its bounds:

Why: AI agents often say "fixed" when nothing actually moved — small layout changes are invisible in screenshots. The UI tree makes them provable:

before:  "bounds": [66, 300, 814, 410]
after:   "bounds": [66, 308, 814, 418]

top 300 → 308: the button provably sits 8px lower. Output is deterministic, so a changed number is always a real change. See the UI tree dump docs for the full workflow.

Supported on all Roborazzi targets: Android/Robolectric, Compose Desktop, and Compose iOS (#883) — same JSON schema and the same annotated-image look everywhere.

Details:

... (truncated)

Commits

• 42b00b5 1.69.0
• e74d48f Merge pull request #886 from takahirom/takahirom/fix-webp-overwrite-truncation
• 241010a Merge pull request #884 from takahirom/tm/uitree-5-release-hardening
• 25251c7 Use assertTrue and assertThrows in annotation hardening test
• ed31f42 Use assertTrue instead of assert in ImageIoFormatOverwriteTest
• 4c602dc Merge pull request #885 from takahirom/tm/optimize-bitmap-to-bufferedimage
• acd9bff Fix WebP golden file corruption when overwriting with a smaller image
• 9dc8c79 Clean up shared outputs in boxed UI tree tests
• 962cb7e Name annotation-writer lambdas in desktop and iOS dump helpers
• 0e22bf3 Signal actual-image writes explicitly to annotated image writer
• 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]

Labels

The following labels could not be found: android, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.