https://kotlinlang.org logo
#library-development
Title
# library-development
r

Rafael Costa

11/25/2021, 11:44 AM
Imagine you have a Compose library that is in beta and you want to start releasing two artifacts per version: one that also uses beta Compose dependencies and another that uses stable Compose dependencies internally. How would you name the two artifacts versions? I was using something like
0.9.0-beta
but now the idea would be something like (just to convey the point, not that I’d call them that, I guess?)
0.9.1-beta-stable
and
0.9.1-beta-beta
.
j

Javier

11/25/2021, 12:33 PM
I would indicate the complete compose version. Version alone can meaning your lib is beta, not using compose beta
And maybe you can publish betas in the future using stable compose version too
r

Rafael Costa

11/25/2021, 12:37 PM
And maybe you can publish betas in the future using stable compose version too
this is what I want now. My library is beta but I want to release artifact with stable compose (atm 1.0.5) and another artifact for compose beta (1.1.0-beta03)
j

Javier

11/25/2021, 1:11 PM
then 0.9.0-beta.13-1.1.0-beta3
beta.13 -> your beta, 1.1.0-beta3 -> compose version
13 was a random number 🙂
👍 1
b

bod

11/25/2021, 1:44 PM
for inspiration: KSP depends on specific versions of the Kotlin compiler, so they put both numbers: https://github.com/google/ksp/releases
👍 2
r

Rafael Costa

11/25/2021, 1:50 PM
ok guys thanks so much for the input. I’ll think about it