Skip to content

feat(provider): add opt-in Android Kotlin registry access - #1

Open
Tojaj wants to merge 1 commit into
mainfrom
feat/android-kotlin-registry-provider
Open

Tojaj wants to merge 1 commit into
mainfrom
feat/android-kotlin-registry-provider

Conversation

@Tojaj

@Tojaj Tojaj commented Oct 16, 2026

Copy link
Copy Markdown
Owner

Let sandboxes resolve Kotlin Android dependencies without granting broad network access. Cover Gradle distributions and plugins, Maven Central, Google Maven, and SDK downloads in one credential-free read-only profile, following the existing opt-in registry pattern.

Scope dl.google.com to /android/** so the grant takes precedence over the baseline Google audit wildcard without conflicting with the Go profile's /go/** entry. Toolchain binaries stay image-provided; verify resolved paths in a derived image before import.

Assisted-by: OpenCode:muse-spark-1.3-contributor-free

@Tojaj
Tojaj force-pushed the feat/android-kotlin-registry-provider branch from 1bd20db to 91a6dbc Compare October 16, 2026 18:56
Let sandboxes resolve Kotlin Android dependencies without granting
broad network access. Cover Gradle distributions and plugins, Maven
Central, Google Maven, and SDK downloads in one credential-free
read-only profile, following the existing opt-in registry pattern.

Scope dl.google.com to /android/** so the grant takes precedence over
the baseline Google audit wildcard without conflicting with the Go
profile's /go/** entry. Toolchain binaries stay image-provided; verify
resolved paths in a derived image before import.

Assisted-by: OpenCode:muse-spark-1.3-contributor-free
@Tojaj
Tojaj force-pushed the feat/android-kotlin-registry-provider branch from 91a6dbc to 11aac21 Compare October 16, 2026 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant