A modern programming language that makes developers happier.

kotlinlang

*Heads up for everyone using Kotlin EAP* :wave:

We’ve added a clear description of all EAP stages to the website, so you know what to expect from each stage:
:point_right:<https://kotlinlang.org/docs/eap.html| https://kotlinlang.org/docs/eap.html>

:kotlin_emoji:Each EAP build is ready to be used with real projects, so you can *try it in practice!*

&gt; *Keep your library up-to-date*. If you're a library author, updating to the new Kotlin version is extremely important. Using older versions could block your users from updating Kotlin in their projects. Working with EAP versions allows you to support the latest Kotlin versions in your library almost immediately with the Stable release, which makes your users happier and your library more popular.
My understanding has usually been the opposite. Updating too quickly can lock consumers out of being able to use your new library version, if for some reason they aren't ready to upgrade Kotlin yet. <@U79JY5TL3> has done some writing on this.

Testing on EAPs is still something you should do as a library author so that any issues can be addressed for when the library is ready to upgrade. But I'm not convinced that upgrading immediately is always the best move.

I'd add a caveat to the library use case:
OSS for the whole world: yeah probably stay reasonably up to date and test against EAP
Closed source private library: To hell with the teams that refuse to look at dependabot/renovate PRs. They don't care enough to update anything, just ship it.

Yea for KMP projects, upgrading KGP forces your consumers to upgrade. Some consumers will like it, others won't. We need <https://youtrack.jetbrains.com/issue/KT-66755/Native-non-JVM-targets-add-support-for-languageVersion|https://youtrack.jetbrains.com/issue/KT-66755/Native-non-JVM-targets-add-support-for-languageVersion>

Hi <@U2VU05RC4>! Actually, we only added the table with EAP builds to the page, the rest of information was there before, so part "*Keep your library up-to-date*." - was always there, it's not something new. But anyway, thank you for the feedback!

In latest releases we received and will receive different interesting features like:
1. `of` operator
2. Unused return value checker
3. Context parameters
and if your library will be more useful with these features  you will need latest Kotlin for library.