Over the weekend I noticed that `detekt-api` `2.0....

# detekt

[seb]

Over the weekend I noticed that detekt-api 2.0.0-alpha.5 (and alpha.4, both built against Kotlin 2.4.0) publishes a Gradle Module Metadata variant set that breaks consumer resolution under Gradle 9.4.1 and 9.6.1 when the Kotlin Compose compiler plugin is on the build. The fully-compatible runtimeElements gets rejected as "no matching variant", so detekt-test can't be resolved. The older alpha.3 with Kotlin 2.3.21 resolves fine; the difference is a testFixturesSourcesElements variant with a detekt-api-test-fixtures capability with no corresponding test-fixtures library variants. This seems to mostly break on macOS and work on the Linux CI.

Is an alpha.6 on the roadmap that would pick up a fix for this, or is there a recommended workaround in the meantime, other than remaining on alpha.3?

[Brais Gabin]

I don't remember to see any issue related with that so I guess this was an unkonwn issue. Could you open an issue on the repo?

[seb]

Will do! Wanna try a couple more things to see if it's me or what, if I confirm it's not me

[seb]

@Brais Gabin github.com/detekt/detekt/issues/9409 seems like the same issue, so it should already be fixed 🙂 just need alpha 6 with the fix to be published

[gammax]

Alpha 5 should contain the fix no?

[Brais Gabin]

No, it landed after it

[seb]

Any hope for an alpha 6 with the fix any time soon?

[gammax]

I can do a alpha 6 later this week

[seb]

Would be really appreciated, Nicola