Skip to content

Chore(deps): Bump androidx.compose.runtime:runtime-livedata from 1.7.7 to 1.10.0#761

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/gradle/androidx.compose.runtime-runtime-livedata-1.10.0
Open

Chore(deps): Bump androidx.compose.runtime:runtime-livedata from 1.7.7 to 1.10.0#761
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/gradle/androidx.compose.runtime-runtime-livedata-1.10.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jan 12, 2026

Bumps androidx.compose.runtime:runtime-livedata from 1.7.7 to 1.10.0.

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps androidx.compose.runtime:runtime-livedata from 1.7.7 to 1.10.0.

---
updated-dependencies:
- dependency-name: androidx.compose.runtime:runtime-livedata
  dependency-version: 1.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Jan 12, 2026
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Jan 12, 2026

Greptile Summary

Overview

This PR updates androidx.compose.runtime:runtime-livedata from version 1.7.7 to 1.10.0 in the Compose sample app. While dependency updates are generally beneficial for security and features, this particular update creates a critical version incompatibility that needs to be addressed.

Critical Issue: Compose Version Mismatch

The build configuration has a fundamental problem with how Compose dependencies are managed:

Current State:

  • Compose BOM: 2024.04.01 (pins most Compose libraries to ~1.6.x)
  • runtime-livedata: Being updated to 1.10.0 (4+ minor versions ahead)
  • activity-compose: 1.10.0 (also explicitly versioned)
  • Kotlin: 1.9.23
  • kotlinCompilerExtensionVersion: 1.5.13

The Problem:
Compose 1.10.0 requires Kotlin 2.0+ or at minimum Kotlin 1.9.x with kotlinCompilerExtensionVersion 1.5.15+. The current configuration uses 1.5.13, creating binary incompatibilities.

More critically, mixing Compose 1.10.0 (runtime-livedata) with Compose 1.6.x (other libraries from BOM) creates version conflicts that can cause:

  • Compilation failures due to missing or changed APIs
  • Runtime crashes with ClassNotFoundException or NoSuchMethodError
  • Unpredictable behavior in Compose functions like observeAsState() (used in CallScreen.kt)

Recommendations

Option 1 (Recommended): Remove the explicit version and let the BOM manage it:

implementation("androidx.compose.runtime:runtime-livedata")  // Version managed by BOM

Option 2: Upgrade the entire Compose stack together:

  • Update BOM to 2024.12.01 or newer
  • Update kotlinCompilerExtensionVersion to 1.5.15
  • Ensure all Compose dependencies are aligned

Additional Finding

There's also a minor version mismatch with the Kotlin serialization plugin (1.9.0 vs project Kotlin 1.9.23), though this is not directly related to this PR.

Impact Assessment

Risk Level: High - This change is likely to break the build or cause runtime failures.

Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Jan 12, 2026

Additional Comments (1)

samples/compose_app/build.gradle.kts
Critical Version Mismatch: Upgrading runtime-livedata to 1.10.0 creates a significant incompatibility with the existing Compose setup:

The Issue:

  • The Compose BOM 2024.04.01 (line 85) pins most Compose dependencies to version ~1.6.x
  • This PR updates runtime-livedata to 1.10.0, which is from a much newer Compose release
  • Compose 1.10.0 requires either:
    • Kotlin 2.0+ (with no kotlinCompilerExtensionVersion specified), OR
    • Kotlin 1.9.x with kotlinCompilerExtensionVersion 1.5.15+
  • Current project uses Kotlin 1.9.23 with kotlinCompilerExtensionVersion 1.5.13 (line 62)

Impact:
This version mismatch can cause:

  • Runtime crashes with ClassNotFoundExceptions
  • Compilation errors due to binary incompatibilities between Compose versions
  • Unexpected behavior in observeAsState() function used in CallScreen.kt (lines 107-109)

Recommendation:
Either:

  1. Upgrade all Compose dependencies together by updating the BOM to 2024.12.01 or newer and updating kotlinCompilerExtensionVersion to 1.5.15, OR
  2. Keep runtime-livedata aligned with the BOM by removing the explicit version and letting the BOM manage it
    implementation("androidx.compose.runtime:runtime-livedata")

This allows the BOM to manage the version and ensures all Compose dependencies are compatible.

Prompt To Fix With AI
This is a comment left during a code review.
Path: samples/compose_app/build.gradle.kts
Line: 85:96

Comment:
**Critical Version Mismatch**: Upgrading `runtime-livedata` to 1.10.0 creates a significant incompatibility with the existing Compose setup:

**The Issue:**
- The Compose BOM `2024.04.01` (line 85) pins most Compose dependencies to version ~1.6.x
- This PR updates `runtime-livedata` to 1.10.0, which is from a much newer Compose release
- Compose 1.10.0 requires either:
  - Kotlin 2.0+ (with no `kotlinCompilerExtensionVersion` specified), OR
  - Kotlin 1.9.x with `kotlinCompilerExtensionVersion` 1.5.15+
- Current project uses Kotlin 1.9.23 with `kotlinCompilerExtensionVersion` 1.5.13 (line 62)

**Impact:**
This version mismatch can cause:
- Runtime crashes with ClassNotFoundExceptions
- Compilation errors due to binary incompatibilities between Compose versions
- Unexpected behavior in `observeAsState()` function used in `CallScreen.kt` (lines 107-109)

**Recommendation:**
Either:
1. **Upgrade all Compose dependencies together** by updating the BOM to `2024.12.01` or newer and updating `kotlinCompilerExtensionVersion` to 1.5.15, OR
2. **Keep runtime-livedata aligned with the BOM** by removing the explicit version and letting the BOM manage it

```suggestion
    implementation("androidx.compose.runtime:runtime-livedata")
```

This allows the BOM to manage the version and ensures all Compose dependencies are compatible.

How can I resolve this? If you propose a fix, please make it concise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Development

Successfully merging this pull request may close these issues.

0 participants