Repository navigation
fix(deps): go back to lifecycle 2.10.0 and compileSdk 36 - #1108
Merged
Merged
Conversation
lifecycle 2.11.0 needs compileSdk 37 and Android Gradle plugin 9.1, and building against 37 stamped that floor into our AARs. Apps on AGP 8, which includes every React Native and Expo app, could not build against 1.2.0. Hold lifecycle below 2.11 in Renovate until they can.
Contributor
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 2
✨ Finishing Touches
Comment |
swolfand
enabled auto-merge (squash)
October 15, 2026 00:10
swolfand
disabled auto-merge
October 15, 2026 00:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
clerk-android 1.2.0 can't be used in apps that build with Android Gradle plugin 8, which includes every React Native and Expo app. Bumping
@clerk/expo-native-componentsto 1.2.0 fails all three Android jobs at:app:checkReleaseAarMetadata(clerk/javascript#10247):clerk-android-api:1.2.0,clerk-android-ui:1.2.0andclerk-android-telemetry:1.1.0require apps to compile against API 37. The Expo app compiles against 36 with AGP 8.11.0, whose highest supported compileSdk is 36.androidx.lifecycle:*:2.11.0requires compileSdk 37 and AGP 9.1.0 or higher.Both floors come from #1077, which moved lifecycle to 2.11.0 and raised
compileSdkto 37 to build it.Changes
lifecyclegoes back to2.10.0andcompileSdkback to36. fix(deps): update dependency androidx.lifecycle:lifecycle-viewmodel-navigation3 to v2.11.0 #1077 also put every lifecycle artifact on one version ref and gave apps a separatetargetSdk; both stay.navigationComposegoes from 2.10.2 to 2.9.8. navigation-compose 2.10.x also needs compileSdk 37 and pulls in lifecycle 2.11, so the two samples that use it (linear-clone,prebuilt-ui) wouldn't build against 36. Only the samples depend on it; it isn't in the published libraries.renovate.jsonholdsandroidx.lifecycle:**below 2.11.0 andnavigation-composebelow 2.10.0, so Renovate doesn't reopen these bumps.After this merges, release 1.2.1. It re-publishes telemetry too. Then point clerk/javascript#10247 at 1.2.1.
Verification
assembleDebug(every module), unit tests for api, ui and telemetry,apiCheck, and lint on the three libraries all pass.:e2epassescheckDebugAarMetadataagainst compileSdk 36, so the published dependency graph needs nothing above 36.releaseRuntimeClasspathfor:source:uiresolves every lifecycle artifact to 2.10.0.verify-clerk-androidbefore release.