Beta: Significant Changes
This is the first, publicly announced, beta release of Compose Hot Reload.
- Stabilized the Gradle API (⚠️ Read about Breaking Changes below)
- Stabilized 'Orchestration Protocol' (⚠️Read about Breaking Changes below)
Gradle Plugin
- ⚠️ breaking: Changed package from
org.jetbrains.compose.reload
toorg.jetbrains.compose.reload.gradle
- ⚠️ breaking: Aligned task naming schema with KGP run tasks
- from
jvmRunHot
->hotRunJvm
(multiplatform) - from
runHot
->hotRun
(jvm)
- from
- Use
mainClass
fromcompose.application
configuration as convention - Support Gradle 9
Core
- Removed slf4j dependency in favor of custom logging implementation
compose.reload.logStdout=true
compose.reload.logLevel=Info
- Removed 'dev' variant from the runtime artifacts: A single 'main' variant for 'hot-reload-runtime-jvm' is published
- Removed relocation markers for old
artifactId
s
DevTools
- Fixed 'ReloadState' when using
explicit reload mode
- Implemented 'coordinated shutdown' to clean up resources when the user application dies
Analysis
- Improve support for Lambdas: Ignore
ComposableSingletons
when resolving transitively dirty scopes
Amper
- Added extension point for Amper to take full control over the recompilation
Compose Multiplatform
- Fix devtools not showing up automatically with Compose Multiplatform 1.9.0-alpha03
- Initial support for changes in compose resources (e.g., adding Strings or Images). Full support (e.g., by automatically refreshing the resources on screen is not yet enabled by default.
Orchestration Protocol
- Stabilized API: Migrated to non-blocking
- Stabilized protocol: v1
Why was beta01 not advertised?
The promotion towards beta was rolled out in two phases. beta01
can be used by clients which are not ready to adapt their build scripts quickly, but require other fixes or functional changes.