4.1.0 contains new ktor3 module :tada:
# koin
a
4.1.0 contains new ktor3 module ๐ŸŽ‰
๐Ÿ™Œ 1
h
Hello Arnaud! I'm just messaging to say that it seems that
ktor3
seems to have fixed the issue indeed. Thabk you very much for releasing the beta version so quickly. If you don't mind, I would like to ask 2 questions. Haha. 1. Do you have an ETA for the final release? 2. When it comes to using
koin-ktor3
, am I right going forward we should be using that module or do you intend to use
koin-ktor
once you release the stable version?
a
1. Do you have an ETA for the final release?
4.1 will be for Q1 2025, time to deliver new features. But while this, I will publish new releases to let you go with it and help test around
When it comes to using
koin-ktor3
, am I right going forward we should be using that module or do you intend to use
koin-ktor
once you release the stable version?
Good question. I would perhaps need to check with JB what they think about. But then we would force people to go with ktor v3. They didn't broke their package space neither, then I would tend to think about upgrading koin-ktor to ktor v3 entirely yes
thank you color 1
h
Thanks for the quick reply. Regarding the first one:
4.1 will be for Q1 2025, time to deliver new features. But while this, I will publish new releases to let you go with it and help test around
Just to give some context, we are using
koin
on a
production
service that actually receives ~50k requests per minute. I'd be happy for us to temporarily release the
production
version using the Beta1. I don't think it is possible to override packages on Maven Central, and I also assume you always bump the version anyway, right? For my second question, I understand and your answer makes plenty of sense. I guess you know a lot more than I do, but perhaps if you wish to continue having
koin-ktor
you could also consider bumping to a major version of
koin
(perhaps
5.x.x
) since it would be a a breaking change, right? Also, do you actually expects that
ktor
team will continue maintaining
ktor v2
? Anyway, I think it should be good for now, just giving you some food for thought. I will keep looking into the docs. For now, I guess I will consider using
4.1.0-Beta1
in Prod. ๐Ÿ˜ƒ Once again, really appreciate your help in this matter and for being so responsive.
a
I don't think it is possible to override packages on Maven Central, and I also assume you always bump the version anyway, right?
yeah, no override on Maven Central. Even if it's beta, I try to track stability of those features at maximum
๐Ÿ™Œ๐Ÿฝ 1
For my second question, I understand and your answer makes plenty of sense. I guess you know a lot more than I do, but perhaps if you wish to continue having
koin-ktor
you could also consider bumping to a major version of
koin
(perhaps
5.x.x
) since it would be a a breaking change, right? Also, do you actually expects that
ktor
team will continue maintaining
ktor v2
?
it might be a direct upgrade, and I will contact JB team to confirm if it make sense to have seperate package or not
๐Ÿ‘€ 1
Anyway, I think it should be good for now, just giving you some food for thought. I will keep looking into the docs. For now, I guess I will consider using
4.1.0-Beta1
in Prod.
Cool ๐Ÿ™‚ Let me know
๐Ÿ‘๐Ÿฝ 1