What about a simple `2.0.0-1.0.20` or `1.9.24-1.0....

# ksp

[Nivaldo H Bondança]

What about a simple 2.0.0-1.0.20 or 1.9.24-1.0.21?

[Jiaxiang]

There is no changes for KSP1 between 1.0.20 and 1.0.21, you should be fine using just 2.0.0-1.0.20 for KSP2 or 1.9.24-1.0.20, whichever works for you.

[Nivaldo H Bondança]

The problem is that there is no maven artifact for 2.0.0-1.0.20 yet. Was it supposed to be one available?

[Jiaxiang]

If you are using KSP1, you should be fine just using 2.0.0-1.0.21

[Nivaldo H Bondança]

My goal was to try to seamless change between Kotlin 2.0.0 and 1.9.24, as that's what we're testing in our (huge and monorepo) codebase.
Currently I am resolving the KSP version dynamically to ${kotlin_version}-1.0.20 and I thought I could keep on doing that. This is why I wanted to check if there no plans to release 2.0.0-1.0.20 or 1.9.24-1.0.21, to know whether I should update my logic here or not

[Nivaldo H Bondança]

Basically we're on Kotlin 1.9.24 and want to migrate to 2.0.0. We're testing things in different parts of the codebase, finding the errors, working on them and iterating on that.
The way we test is with flag that tells our build system which Kotlin version to use.

[Jiaxiang]

currently we don’t have a plan to do a release for 2.0.0-1.0.20 due to the reasons above. can you workaround it by manually adding versioning logic for KSP?

[Nivaldo H Bondança]

Sure thing! 🙂

Thank you so much for clarifying things 🙂