Why is latest beta-6 using Kotlin 2.0.0-RC1?

[damianpetla]

Question

Hey! I will be honest and I admin that I haven't tried new beta-6 yet but the main reason was seeing Kotlin 2.0.0-RC1. We are using KMP with Apollo and every time there is Kotlin upgrade things break all over the place and we have to update different libs etc.
So my question is: was it really necessary to upgrade it to Kotlin 2.0.0? If so I am curious why, if not, would it be possible for the future to stay on the latest stable Kotlin version please?

[martinbonnin]

Hi 👋 The general idea is:

• stable Apollo versions (3.8 right now) are conservative when it comes to Kotlin versions and will always use latest stable (or even older one if there's no reason to upgrade)
• alphas/beta use latest KGP but target stable apiVersion/languageVersion.
  • On JVM projects, there should be no issue using apollo:4.0.0-beta.6 with Kotlin 1.9.x.
  • It's a bit less clear on Native/JS because there's no languageVersion support for native (related Youtrack)

What we've seen so far is that KMP projects usually need to track the Kotlin version pretty closely because that part of the ecosystem is moving quite fast. If it's slowing down we'll consider being more conservative for alphas/betas as well but being able to use latest build tools while targetting older binaries seems pretty important for the ecosystem overall. I wouldn't give up on this without trying it a bit more. If you have specific issues, please share them so we can make sure the ecosystem evolves smoothly.

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Kotlin usage and allow us to serve you better.