<https://github.com/JetBrains/kotlin/releases/tag/...
# feed
a
v
But as usual, not before the blog post at https://blog.jetbrains.com/kotlin/ appears 😉
e
as usual, wait for the announcement because releasing involves several different moving pieces which are not synchronized
a
Is it a real warn for me a just a tip for people reading the thread ? If it is then I'm sorry, I can delete the post if needed
every single release works this way
v
It is a real warn. For example the artifacts could not be available, the Gradle plugin not published, .....
t
there should really be some effort on having this synchronization. one can always some brain into it, but tool like renovate will start to pick 1.8.10, causing maintenance work on some people (hence why I don’t use renovate or any of those tools)
j
I guess there are many people that get notified automatically when there's new "release" on github ....means we can at least attempt to try to use it but realise as you say that artifacts might not be there (though don't think I've run in to that yet)
v
You cannot do much about the synchronization probably, as JetBrains does not control all the moving parts like Maven Central, Gradle Plugin Portal, and whatnot else
j
Caveat emptor 🙂
e
just considering two of them moving pieces. Tag GitHub first, and then build and upload to Maven? then people see the release before artifacts are available. Build and upload to Maven first, and then tag GitHub? then there is are artifacts without corresponding code.
t
maybe it is just a matter of size, but how do libraries do? kotlin is the only jar I am not suppose to use once it is available in maven central (side note: tagging on github can happen first imo, ofc nobody has to use maven central or those jar distribution services, but that is what they are for and what automatic tools check to figure out new stuff is out)
h
You could create a tag without a GitHub release 🙂
e
Kotlin is much larger than a library
t
then again, for me it is not a real problem, I am just wondering if there is really no better way of handling the release process (but I am no expert)
e
anybody releasing to both Maven Central and GPP has synchronization issues. but in Kotlin's case, there's also all the Konan artifacts, the IDE plugins, the website docs…
k
It’s not like they’re going to unpublish this because you saw the tag before the official announcement
e
p
Do the users of latest IntelliJ 2022.3 have to wait for IDEA update to get the new kotlin plugin again?
v
I never needed to wait for an IDE update. I'm on 2022.2.3 and already have the new plugin
p
I know, I have it on my other machine with older IJ. But on 2022.3 we had to wait for IDE update when 1.8 was released and apparently it's a thing now 😔
😶 1