https://kotlinlang.org
Join Slack
Build `1.0.0-alpha4-build362` is out with support for Kotlin 1.5.31
# compose-desktop
k
Build 
1.0.0-alpha4-build362
is out with support for Kotlin 1.5.31
🔥 9
🚀 5
❤️ 5
K 14
💪 4
o
Seems like compose web artifacts are not up to date. The last build in https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/web/web-core/ is 
1.0.0-alpha4-build348
. Is this intentional?
k
I'm getting the 362 builds, but not sure where they are coming from.
o
If I spotted it correctly, there is no web artifact either in your list. My 
gradle dependencies
lists:
Copy code
+--- org.jetbrains.compose.web:web-core:1.0.0-alpha4-build362 FAILED
\--- org.jetbrains.compose.runtime:runtime:1.0.0-alpha4-build362
     \--- org.jetbrains.compose.runtime:runtime-js:1.0.0-alpha4-build362
So the 
runtime
is there. 
web-core
is not.
h
Yup, there is no 
web-core
for 
362
.
o
web-core
seems out of sync since >348: 356 and 361 are missing, too.
k
348 is the last published release on GitHub, but somehow we do have later binaries on their space
d
⚠️ This may not be a problem If 
362
was just found by looking at the artifact repository, then I have observed many times before that the web components always lag behind in upload. Maybe they are build separately or just take longer to compile for some reason; but wait a few hours and this build may work as expected. Patience 🙂👌
It would help with planning around this, to know when is the intended release date for 
1.1.0
?
k
That's probably for #compose as JB has its own naming sequence
d
Whoops, I posted in entirely wrong thread 🤦 ... working on too many issues RN, lucky me.
h
web-core 362
is uploaded since 
2021-09-28 07:54 UTC
o
Yep, now it's there. @darkmoon_uk Web component builds lagging behind the others does not explain why there's no 356 and 361 for the former.
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by