Imagine you have a Compose library that is in beta...

# library-development

[Rafael Costa]

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.

[Javier]

I would indicate the complete compose version. Version alone can meaning your lib is beta, not using compose beta

[Javier]

And maybe you can publish betas in the future using stable compose version too

[Rafael Costa]

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)

[Javier]

then 0.9.0-beta.13-1.1.0-beta3

[Javier]

beta.13 -> your beta, 1.1.0-beta3 -> compose version

[Javier]

13 was a random number 🙂

[bod]

for inspiration: KSP depends on specific versions of the Kotlin compiler, so they put both numbers: https://github.com/google/ksp/releases

[Rafael Costa]

ok guys thanks so much for the input. I’ll think about it