oss-licenses-plugin forces compose material3 alpha version

[mobielbekeken-thijs]

Describe the bug
After adding the oss-licenses-plugin to my app, an alpha version of compose material3 is used.

To Reproduce
Follow the general installation steps https://developers.google.com/android/guides/opensource

Run gradle task help > dependencies.
This will display:

+--- androidx.compose.material3:material3 -> 1.5.0-alpha17 (*)
\--- com.google.android.gms:play-services-oss-licenses:17.5.1
     +--- androidx.activity:activity:1.12.1 -> 1.13.0 (*)
     +--- androidx.activity:activity-compose:1.12.1 -> 1.13.0 (*)
     +--- androidx.compose.foundation:foundation:1.10.0 -> 1.11.0-beta02 (*)
     +--- androidx.compose.foundation:foundation-layout:1.10.0 -> 1.11.0-beta02 (*)
     +--- androidx.compose.material:material-icons-core:1.7.8
     |    \--- androidx.compose.material:material-icons-core-android:1.7.8
     |         \--- androidx.compose.ui:ui:1.6.0 -> 1.11.0-beta02 (*)
     +--- androidx.compose.material3:material3:1.5.0-alpha17 (*)

Without the library, material3 will not use this alpha version:

+--- androidx.compose.material3:material3 -> 1.4.0

Expected behavior
A stable, non-alpha version of material3 will be used.

Desktop:

• Gradle version: 9.5.1
• Android Studio version: Android Studio Panda 4 | 2025.3.4 Patch 1
• Plugin name and version: OSS Licenses 17.5.1

[blueguy]

We encountered the same issue after upgrading play-services-oss-licenses to 17.5.1.

In addition to the Material3 alpha transitive dependency already reported here,
we also found that it pulls in alpha versions of Lifecycle Compose libraries:

• androidx.lifecycle:lifecycle-runtime-compose:2.11.0-alpha03
• androidx.lifecycle:lifecycle-viewmodel-compose:2.11.0-alpha03

Our project pins these at the stable 2.10.0, and the build fails with:

Could not resolve androidx.lifecycle:lifecycle-runtime-compose:2.11.0-alpha03.
  Required by:
      project ':app' > com.google.android.gms:play-services-oss-licenses:17.5.1
  > Requested library required higher version (2.11.0-alpha03)
    than what is declared in the Version Catalogs (2.10.0).

So the issue is not limited to Material3 — 17.5.1 transitively forces multiple
alpha-channel Jetpack libraries into projects that have stable-only policies.

[michal-luszczuk]

+1 for this issue.
In our project we are using BottomSheetScaffold component from androidx.compose.material3 library (and we were on 1.4.0 version declared on our side).
And it was really confusing that it stop to work as expected after updating the play-services-oss-licenses library from 17.4.0 to 17.5.1.
So this library shouldn't use any alpha dependencies under the hood, because it can easily lead to serious unexpected errors in production apps.

[KatieBarnett]

I'm seeing this as well - the lifecycle update is causing lifecycle owner conflicts which is resulting in extra data fetches for me. I haven't yet updated to SDK 37 so possibly this would fix it when they are all in sync, I can't even downgrade to 17.4.0 as this has a crash with the stable version of Navigation 3 (and this used an alpha)