A modern programming language that makes developers happier.

kotlinlang

how do the compose desktop builds work in terms of syncing with the core compose framework? For example, does build 0.5.0-build220 contain changes from the compose core done last friday? in this case it would be change made in the compose "framework" package

We migrated our builds to our <https://github.com/JetBrains/androidx/commits/jb-main|fork>.

We plan to periodically rebase it on `androidx-main` (core Compose)

There will be some commits on the top: for Compose for Web, and for desktop that still not merged into androidx-main).

After 1.0 we will probably rebase only on a stable core Compose (probably a version will be the same, or at least first two numbers, not sure yet)

there were some bugs introduced in 0.4.0 that are causing rendering issues in existing apps, it looks like the one im concerned with was fixed last friday. when is the next rebase scheduled?

The new build with the latest `androidx-main` will be built soon (in an hour probably)

<https://github.com/JetBrains/compose-jb/releases/tag/v0.5.0-build221>

Should that build have `awaitApplication` and the new Window  API?

It is only in 0.4.0 for now, we are still in the middle of migration, so we have multiple branches :slightly_smiling_face: <https://github.com/JetBrains/androidx/tree/release/v0.4.0|0.4.0>, <https://github.com/JetBrains/androidx/tree/jb-main|jb-main> (0.5.0-build) and <https://github.com/JetBrains/androidx/tree/androidx-main|androidx-main>.

But soon we will add the new API to jb-main

We have completely migrated to the new branch, `0.5.0-build223` contains WinAPI

Does web still depend on coroutines 1.4.3?

Should be 1.5.0, the commit with it exists in build223