would it be possible to cut a 2.0.0-alpha01 releas...

# detekt

[jbarr]

would it be possible to cut a 2.0.0-alpha01 release of Detekt to make it easier for companies to move forward w/ K2 migrations & updating their custom rules? that wouldn't rule out more breaking changes & would allow stable artifacts that aren't snapshots

[Brais Gabin]

🤔 interesting. how does it breaks for you? I have this PR https://github.com/BraisGabin/detekt-compiler-rules/pull/84/files green. And those are custom rules using the latests stable version of detekt compiled using kotlin 2.0.0

[jbarr]

@Brais Gabin it breaks for us since we are using Buck as our build system for our monorepo which only allows 1 version of Detekt & 1 of Kotlin. there is no idea of configurations. we are trying to build our monorepo with K2 (using language version 2) including tests for custom detectors that fail with the error message below

FAILURE com.ubercab.presidio.detekt.rules.ForbiddenMethodDetectorTest detect_matchOnCompanionObject: org.jetbrains.kotlin.cli.jvm.compiler.NoScopeRecordCliBindingTrace: method 'void <init>()' not found
java.lang.NoSuchMethodError: org.jetbrains.kotlin.cli.jvm.compiler.NoScopeRecordCliBindingTrace: method 'void <init>()' not found
	at io.gitlab.arturbosch.detekt.test.KotlinCoreEnvironmentExtensionsKt.getContextForPaths(KotlinCoreEnvironmentExtensions.kt:14)
	at io.gitlab.arturbosch.detekt.test.RuleExtensionsKt.lintWithContext(RuleExtensions.kt:46)
	at io.gitlab.arturbosch.detekt.test.RuleExtensionsKt.compileAndLintWithContext(RuleExtensions.kt:61)
	at com.ubercab.presidio.detekt.rules.ForbiddenMethodDetectorTest.detect_matchOnCompanionObject(ForbiddenMethodDetectorTest.kt:126)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)