-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert material3 to 1.3.1 #1868
Conversation
Could we get the reason behind this change? I already had some implementations of some of the new components and this will break my app (which will be a pain to get around it, although its was dev versions and its understandable) |
It's due to difference in release cycles. Google won't release stable material3 1.4 together/before with Compose 1.8, but on multiplatform it shares the same version. Due to stability expectations we cannot release beta/stable version based on Google's alpha version. We're thinking how to gracefully separate this in future versions, but for 1.8 we have to revert it to 1.3.x state. You can continue using alpha03 version for material3 if you want to experiment with new APIs from there |
…le` afterward (#1601) # Conflicts: # compose/ui/ui-test/src/skikoTest/kotlin/androidx/compose/ui/test/TestBasicsTest.kt # navigation/navigation-compose/src/commonTest/kotlin/androidx/navigation/compose/NavHostTest.kt
…1696) These are preparation to build Compose 1.8.0-alpha01 from `jb-main` branch. 1. Set the default version to 9999.0.0-SNAPSHOT. It is needed for pinning, more in the code comment. **Alternative** Move versioning from CI to `libraryversions.toml`. It will contain all next versions we need to publish, and they are always greater than the pinned versions. This requires some work and I didn't plan it in the short term. **Disadvantage** We can accidentally publish it to the dev repo. But users won't see it in the suggestions because it is `-SNAPSHOT`. This is also true for the alternative, so we have this disadvantage anyway. 2. Pin all dependencies to be able to not release them. Not pinned dependencies: - collection (new API needed) - core (new lib core-uri) - shapes (no stable version) ## Testing 1. Build ``` ./gradlew publishComposeJbToMavenLocal ``` 2. Check module files 3. Sync and run the version on the desktop template 4. run1, runDemo # Conflicts: # compose/animation/animation-core/build.gradle # compose/foundation/foundation-layout/build.gradle # compose/foundation/foundation/build.gradle # compose/material/material/build.gradle # compose/runtime/runtime/build.gradle # compose/ui/ui-graphics/build.gradle # compose/ui/ui-test-junit4/build.gradle # compose/ui/ui-test/build.gradle # compose/ui/ui-text/build.gradle # compose/ui/ui-unit/build.gradle # compose/ui/ui/build.gradle # lifecycle/lifecycle-viewmodel-savedstate/build.gradle # navigation/navigation-common/build.gradle # navigation/navigation-compose/build.gradle # navigation/navigation-runtime/build.gradle # savedstate/savedstate/build.gradle
# Conflicts: # compose/runtime/runtime/build.gradle # compose/ui/ui/build.gradle
53e5c1f
to
1df3651
Compare
# Conflicts: # buildSrc/private/src/main/kotlin/androidx/build/AndroidXMultiplatformExtension.kt # compose/material3/material3/api/desktop/material3.api # compose/runtime/runtime/src/nonEmulatorCommonTest/kotlin/androidx/compose/runtime/snapshots/SnapshotStateMapTests.kt # gradle/libs.versions.toml # navigation/navigation-compose/build.gradle # navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/DialogNavigator.kt # navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/NavControllerViewModel.kt # navigation/navigation-runtime/src/jbMain/kotlin/androidx/navigation/NavControllerViewModel.jb.kt
…h WeakMap (#1752) # Conflicts: # lifecycle/lifecycle-viewmodel-savedstate/src/jvmMain/kotlin/androidx/lifecycle/serialization/SavedStateHandleDelegates.jvm.kt # navigation/navigation-runtime/src/jsMain/kotlin/androidx/navigation/internal/Utils.js.kt
Since `PredictiveBackHandler` were previously commonized (without actual implementation yet), it's no longer necessary to wrap usages of it into expect/actual. It fixes missing implementation of `DrawerPredictiveBackHandler` on non-Android platforms. Fixes https://youtrack.jetbrains.com/issue/CMP-1301 and https://youtrack.jetbrains.com/issue/CMP-7309 ## Release Notes ### Fixes - Multiple Platforms - Fix missing implementation on non-Android platforms for `ModalDrawerSheet` overload with `DrawerState` argument
…pose modules. # Conflicts: # navigation/navigation-compose/build.gradle # navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/NavHost.kt
1df3651
to
c50e615
Compare
CMP 1.8.0 will contain Material 1.3.1, not Material 1.4
Fixes https://youtrack.jetbrains.com/issue/CMP-7633/Revert-material3-to-1.3.1-state-for-CMP-1.8.x-release
Better to review commit by commit.
From:
I chose:
compose/material3/material3
.Testing
Release Notes
Breaking Changes - Multiple Platforms
1.4.0-alpha07
to1.3.1
because 1.4.0 Stable will be released only after CMP 1.8.0. As a workaround to continue using the new API, replace: