A modern programming language that makes developers happier.

kotlinlang

Just an observation that the continued presence of the `0.6.x-compat` artifact is a minor ongoing headache.

By default, Gradle resolves `0.8.0-0.6.x-compat` as higher than `0.8.0` so for those of us not using the `-compat` lib, we add a bunch of conflict resolution rules to prevent it from sneaking in transitively somewhere. A recent example is the ktor 3.6.0 update which added a transitive dependency on `0.6.x-compat`.

Will the compat version of the lib be going away soon?

Hi! A short answer: `0.6.x-compat` should go away in 0.10.0.

That said, `0.8.0-0.6.x-compat` being higher than `0.8.0` is entirely intentional, and you shouldn't add conflict resolution rules. If one of your dependencies itself depends on `0.6.x-compat`, that means that either 1) the maintainers made a mistake, or 2) some code paths rely on `kotlinx.datetime.Instant` and will throw an exception if they can't find it. `0.6.x-compat` being higher than the non-compat version prevents the latter.

You can live in a `0.6.x-compat`-free world today if all of your dependencies do a good job and don't depend on a soon-to-be-removed API!

Thanks for the clarification. I'll remove the conflict resolution rules.

I think it was probably an accident for Ktor to introduce this dependency, but I haven't dived into it to confirm.

This could be an accident. They had a task to migrate to `kotlin.time.Instant`, and the task is marked as completed: <https://youtrack.jetbrains.com/issue/KTOR-8635|youtrack.jetbrains.com/issue/KTOR-8635>