Why is `kotlin wrappers` already depending on 1 8 20 It is n

Question

Why is `kotlin wrappers` already depending on 1 8 20 It is not yet officially released confused

Ayfri · Answer

You can already install 1 8 20 the EAP docs are already listing a lot of the changes from this update

Vampire · Answer

You can use it yes it is available on Maven Central But you shouldn t As with every release it needs a few days until everything is in place and until the Blog post appears it is not officially released and should not be used

turansky · Answer

gt You can use it yes it is available on Maven Central gt But you shouldn t Why it doesn t work the same way for `kotlin wrappers` slightly smiling face

Vampire · Answer

Because you do not have such a rule that releases are only to be used when officially announced

Vampire · Answer

Besides that this procedure is disturbing and unnerving especially with people using automatic dependency update bots and then wonder why things do not work properly if they use half released versions

turansky · Answer

How bots understand that new version of Kotlin can be used Is there special flag officially announced

Vampire · Answer

Unfortunately not that s exactly the problem As far as I know people using such bots and being aware of this aweful situation configure it either to ignore Kotlin or to delay suggesting a Kotlin update for 1 or 2 weeks in which time it usually is officially ready

turansky · Answer

From our side it s also important to know that we are compatible with new Kotlin version face with raised eyebrow

Vampire · Answer

Of course but depending on a not fully released version is like depending on an rc or snapshot or similar It is bad to do so especially in a library I intended to switch to latest version and suddenly got my Kotlin version upgraded to a not fully release version

Vampire · Answer

Besides that you usually should depend on the lowest version of dependencies you support not on the latest Like it is now `kotlin wrappers` latest version says I need 1 8 20 and nothing less

turansky · Answer

Are you from Java world slightly smiling face

Vampire · Answer

Yes but that shouldn t make any difference

Vampire · Answer

Especially as that is Gradle logic and Maven logic and Ivy logic and Npm logic not Java logic

turansky · Answer

gt Like it is now `kotlin wrappers` latest version says I need 1 8 20 and nothing less It s what we really check on our projects

turansky · Answer

I mean usually we check wrappers on latest version only

Vampire · Answer

Yeah well if that is what you want to say it s fine except for the fact that it is a not fully released version I tend to be more open to older versions in my library projects to be a bit more compatible Not everyone can always immediately use latest versions of things especially in bigger projects slightly smiling face

turansky · Answer

gt Not everyone can always immediately use latest versions of things especially in bigger projects slightly smiling face I suppose they don t update wrappers every day slightly smiling face

turansky · Answer

gt I tend to be more open to older versions in my library projects to be a bit more compatible Special notes <https github com JetBrains kotlin wrappers blob master CHANGELOG md pre527|in CHANGELOG>

Vampire · Answer

Don t know what you mean Besides that it is not Kotlin 1 8 20 support but Requires now Kotlin 1 8 20 I have no idea why you answer with that link to the quoted statement Yes you notify your users about the 1 8 20 move That was not the point

Vampire · Answer

Well let s just stop it here You want to only support the latest Kotlin version always and that is fine it is your project And you want to require a not yet fully released version that s not so fine but welll it is your project and I just don t upgrade further until it is officially released like with other libs that have the funny idea to depend on unfinished work slightly smiling face

turansky · Answer

< Vampire> Your comments are important But I can t use it directly It doesn t work the same way as for Java libraries unfortunately I have related problems with versions Android needs Kotlin `1 8 10` Kotlin JS needs Kotlin `1 8 20` what would be fine solution

Vampire · Answer

Well don t use a not fully released version smile

Vampire · Answer

But other than that just normal conflict resolution If 1 8 10 is supported 1 8 20 should too so default conflict resolution in Gradle would pick 1 8 20

turansky · Answer

Compose won t support Kotlin `1 8 20` next this week

turansky · Answer

Official announcement will change nothing

Vampire · Answer

They only support an exact specific version o O

Vampire · Answer

Well that s even worse than `kotlin wrappers` then smile

turansky · Answer

We have releases for all stable Kotlin versions slightly smiling face

turansky · Answer

And even for not fully released

turansky · Answer

For my project Kotlin `1 8 20` works fine right now With required fixes for IR compiler

turansky · Answer

gt They only support an exact specific version o O `1 8 0` supported officially

Vampire · Answer

gt Compose won t support Kotlin `1 8 20` next this week Did you mean will not support as in will not officially announce that they support it or as in it fails if you try to use 1 8 20

Vampire · Answer

Because any sane project I know means with supports version x y z x y z and any newer version or at least within the same major or minor version smile

turansky · Answer

gt it fails if you try to use 1 8 20 Yes

Vampire · Answer

cry

Vampire · Answer

But well there you have why it is bad if some libraries force you to always the latest version smile

turansky · Answer

Compose forces you to use previous version slightly smiling face

Vampire · Answer

Present version you said it works with 1 8 10 stuck out tongue

turansky · Answer

Only with suppress

Vampire · Answer

But yeah didn t say that is nice either But the more libraries force single specific versions the worse it is to combine them in a project

Vampire · Answer

Good old joy of dependency hell smile

Landry Norris · Answer

They said when Compose was first released that the Kotlin plugin SDK isn t quite stable yet in terms of breaking changes I believe the goal was to change this in Kotlin 2 0 but not 100 sure if that s on track Because of this Compose needs to be modified for each Kotlin version

ephemient · Answer

Compose has multiple parts The Compose compiler plugin is fairly strictly tied to exact compiler releases The rest of the runtime is not neither to the Kotlin version nor the compiler plugin version