I’ve updated my project to Kotlin 1.8.10 and pulled in detekt v1.23.0-RC1. Does the new version chec...

# detekt

[Travis Miehm]

I’ve updated my project to Kotlin 1.8.10 and pulled in detekt v1.23.0-RC1. Does the new version check in the runner need to be so restrictive, or would checking for a match on major and minor parts of the version be sufficient? Are there anticipated problems when detekt is compiled with 1.8.20 but running with 1.8.10, for example?

[Brais Gabin]

There is not restrictions between those two

[Brais Gabin]

You can use whatever version you want and they should work.

[Travis Miehm]

I get this error when running my detekt gradle task

detekt was compiled with Kotlin 1.8.20 but is currently running with 1.8.10.

This is not supported. See https://detekt.dev/docs/gettingstarted/gradle#dependencies for more information.

[Travis Miehm]

From here, looks like

[Brais Gabin]

https://detekt.dev/docs/next/gettingstarted/gradle#gradle-runtime-dependencies

[Brais Gabin]

The documentation is not released so the link doesn't point to the right site

[Brais Gabin]

if you follow my link will find a rational about what's going on.

[Brais Gabin]

If you don't find that documentation usefull please open an issue so we can improve it. This is new for this version.

[Travis Miehm]

Cool, I can give that work around a shot. Thanks for the link!

I guess in general, I would expect versions that differ at the Patch level to be compatible with each other. But having never paid close attention to the compiler APIs, I don’t know if that’s true for kotlin-compiler-embeddable.

[Brais Gabin]

Sadly it's not because it is not a public api yet.

[Travis Miehm]

Sounds good. Thanks!