Is there something potentially wrong with 1.3.60? Seems strange that it’s been released since Friday but nothing on the master branch changelog, releases, or any comms/announcements

There's always a lag between potential release and any announcements. I suspect some of it is just it takes time to create the Blog post, and some of it may be an opportunity for super eager people to notice, install, and find any potential nasty bugs before they put out the blog post. That's my theory, anyway.

maybe, I’ve never seen a several day lag though

@Zac Sweers what do you mean atomicfu was updated to 1.3.6?

I thought it was already present in 1.3.50 though?

Probably waiting on the official Kotlin libs to finish their upgrades to 1.3.60 before making the release announcement

My gut says they're waiting for at least

kotlinx.coroutines

(native multithreading), to announce them together.

Kotlinx.serialization was not updated to release 1.3.60 yet

I doubt this release of kotlinx.coroutines is going to have native multithreading

is native multithreading via coroutines a confirmed 1.3.60 feature?

not that I know of

that would be great if it was but I didn’t think so either

I'll have a link somewhere. One sec.

Oh, I remember that thread

It's not set in stone though. I'm just guessing.

Yeah. I’m hoping it comes though, I’ve been waiting for native multithreading for nearly 6 months now 😅

I remember around this time last year, someone at KotlinConf predicted multi-threading coming out in February or so. It's really been a while.

IntelliJ was offering 1.3.60 as an update, and now it isn't, so it's possible they actually had pulled the release trigger and then backed it out quickly for some reason.