Skip to content

scope dependency submission to releaseRuntimeClasspath#8

Merged
pzverkov merged 1 commit into
mainfrom
update/scope-dependency-submission
Jun 12, 2026
Merged

scope dependency submission to releaseRuntimeClasspath#8
pzverkov merged 1 commit into
mainfrom
update/scope-dependency-submission

Conversation

@pzverkov

Copy link
Copy Markdown
Member

Limits the submitted dependency graph to what the published library actually ships, by setting DEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS: releaseRuntimeClasspath on the gradle dependency-submission action.

Why

netty, wire, and httpclient reach the dependency graph only through build/test tooling (Android Unified Test Platform / grpc-netty, androidx.benchmark, UTP) - never the AAR or app runtime. Submitting every configuration means Dependabot flags a stream of advisories against those transitives that cannot affect SDK consumers, which is the whack-a-mole we have been doing (alerts #21-#35).

After this change the graph contains only releaseRuntimeClasspath (androidx.core, kotlin-stdlib, androidx.annotation, ...). Dependabot will auto-close the existing build-tool alerts on the next run and stop opening new ones for transitives we do not ship.

Trade-off

Advisories in genuine build-time tooling will no longer surface here. That is the intent - those belong to the AGP/test-platform toolchain, not the SDK. The forced versions in settings.gradle.kts stay as-is (harmless; can be trimmed later if desired).

No code or published-API change.

Report only the dependencies that ship in the published library by setting DEPENDENCY_GRAPH_INCLUDE_CONFIGURATIONS to releaseRuntimeClasspath. Build and test-tooling transitives (netty via the android test platform, wire via androidx.benchmark, httpclient via UTP) are never in the AAR, so Dependabot stops flagging advisories that cannot affect SDK consumers.
@pzverkov pzverkov merged commit f738997 into main Jun 12, 2026
4 checks passed
@pzverkov pzverkov deleted the update/scope-dependency-submission branch June 12, 2026 10:49
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