It seems like kotlin 2.2.10 is out but there hasn'...

# meta

[dave08]

It seems like kotlin 2.2.10 is out but there hasn't been any announcement?

[Zach Klippenstein (he/him) [MOD]]

Did it just come out?

[Stefan Oltmann]

4 days ago on GitHub

[Zach Klippenstein (he/him) [MOD]]

Exactly

[dave08]

I saw some libraries already updated to it, I was hesatant to update, since they always say to wait for the anouncement... but it usually comes quicker...

[dave08]

The funniest thing, is that the docs are at version v2.2.10 (on top) and there's not even a what's new section yet...

[dave08]

I guess it's taking a while to roll out everything...

[Stefan Oltmann]

The GitHub release notes are announcement enough for me. 😉

[dave08]

It means everything important is already rolled out for use?

[Stefan Oltmann]

I've no idea. I just try to keep up with the latest and greatest versions of all libs and frameworks and if something isn't working I usually find out quickly. 🙂

[Todd]

Do they typically announce the x.x.10s? Unless I'm missing something there wasn't an announcement for 2.1.10. Probably because it's typically just a bug fix release.

[dave08]

Fair enough, but like I said before, the different parts of the ecosystem need to go up... so it's fine not to have a blog post, but a quick #C0922A726 from @Alina Dolgikh [JB] when it's useable would still be nice, no?

[Stefan Oltmann]

For my libraries I usually don't announce bugfix releases... major or minor releases that add new features to talk about are more interesting.

If you fear of missing out on a new Kotlin version you can Watch http://github.com/jetBrains/kotlin releases. That's what I do.

[ephemient]

it seems to happen sometimes that the Github release gets created before the artifacts are done uploading to maven central, so if you update right away, your build will fail, and then continue to fail for another day while your local maven cache remembers that the artifact doesn't exist

[dave08]

So when can we actually rely on when a version was fully released? Just wait a day or update and cross your fingers?

[Stefan Oltmann]

Just wait two days, that should be fine.

[Stefan Oltmann]

I have the same with my libs... The GitHub Action releases it and pushes that to Maven Central.
But you need to login there and hit a button. That's a manual process after GitHub CI is done.
And after that the system takes some time to publish the package.

[Stefan Oltmann]

I usually don't update the very minute I see the GitHub release. It's just more like taking a note of "need to update libs in the next days"

[Stefan Oltmann]

Sometimes Maven Central only takes an hour to have the new package available, sometimes longer.
Was never longer than 24 hours. I think they have a lot of caches there in place. It's fine.

[dave08]

So I guess for a Kotlin bug fix release it would be the same, thanks 👍🏼!

[Alina Dolgikh [JB]]

Hi folks! There was already an announcement on Twitter, so we must have missed it here. Let me publish it now to make it official K