Skip to content

Bump Ditto SDK to 4.14.4-rc.3 across all quickstart apps#273

Closed
Kristopher Johnson (kristopherjohnson) wants to merge 1 commit intomainfrom
kj/bump-sdk-4.14.4-rc.1
Closed

Bump Ditto SDK to 4.14.4-rc.3 across all quickstart apps#273
Kristopher Johnson (kristopherjohnson) wants to merge 1 commit intomainfrom
kj/bump-sdk-4.14.4-rc.1

Conversation

@kristopherjohnson
Copy link
Copy Markdown
Collaborator

@kristopherjohnson Kristopher Johnson (kristopherjohnson) commented Apr 28, 2026

⚠️ DO NOT MERGE

This PR pins the Ditto SDK to a release candidate (4.14.4-rc.3) and exists solely so we can build and smoke-test the RC in our quickstart apps. It must not be merged into main.

Summary

Bumps the Ditto SDK from 4.14.34.14.4-rc.3 across every quickstart app currently pinned to a 4.x version, with regenerated lockfiles.

Apps updated: android-java, android-kotlin, cpp-tui, dotnet-maui, dotnet-tui, dotnet-winforms, flutter_app, javascript-tui, javascript-web, react-native, react-native-expo, rust-tui, swift.

Excluded (5.x, preview, or no committed SDK pin): kotlin-multiplatform, java-server, java-spring, go-tui, edge-server, android-cpp.

Pinning approach

All flexible version constraints were tightened to exact pins so the smoke-test result is unambiguous about which RC build was tested:

  • rust-tui/Cargo.toml: =4.14.4-rc.3
  • flutter_app/pubspec.yaml: no caret
  • javascript-tui/package.json, javascript-web/package.json: no caret
  • swift/Tasks.xcodeproj: kind = exactVersion (was upToNextMajorVersion)

react-native and react-native-expo already used exact pins.

Local verification

App Status
rust-tui cargo build
javascript-tui npm run build
javascript-web npm run build
dotnet-tui dotnet build
cpp-tui make build (downloads SDK 4.14.4-rc.3)
android-java ./gradlew :app:dependencies resolves live.ditto:ditto:4.14.4-rc.3
android-kotlin ✅ same
swift xcodebuild clean build for iOS Simulator
flutter_app flutter build apk --debug
react-native ✅ Metro bundle
react-native-expo yarn install resolves rc.3 (Expo project; full bundle deferred to CI)
dotnet-maui dotnet build for net9.0-ios, net9.0-maccatalyst, and net9.0-android
dotnet-winforms skipped (Windows-only target)

Note: Earlier RC 4.14.4-rc.1 had a live.ditto.AppLifecycleListener$Companion duplicate-class issue that broke the dotnet-maui Android target. rc.3 resolves that.

Linear

Closes SDKS-3229
Closes SDKS-3230
Closes SDKS-3231

Test plan

  • CI green across every per-app workflow
  • Smoke test C++ quickstart (cpp-tui) against the RC — SDKS-3231
  • Smoke test Flutter quickstart against the RC — SDKS-3230
  • Smoke test React Native quickstart against the RC — SDKS-3229

Updates android-kotlin, android-java, cpp-tui, dotnet-tui, dotnet-maui,
dotnet-winforms, flutter_app, javascript-tui, javascript-web,
react-native, react-native-expo, rust-tui, and swift to Ditto SDK
4.14.4-rc.3 for release-candidate testing.

All flexible-version constraints are exact pins (=, no caret,
exactVersion) so the smoke-test result is unambiguous about which RC
build was tested:

- rust-tui Cargo.toml: =4.14.4-rc.3
- flutter_app pubspec.yaml: no caret
- javascript-tui/javascript-web package.json: no caret
- swift project.pbxproj: kind = exactVersion (was upToNextMajorVersion)

react-native and react-native-expo already used exact pins.

kotlin-multiplatform/, java-server/, java-spring/, go-tui/, edge-server/,
and android-cpp/ are unaffected (they pin to 5.x or have no committed
SDK reference).
@kristopherjohnson Kristopher Johnson (kristopherjohnson) deleted the kj/bump-sdk-4.14.4-rc.1 branch April 28, 2026 20:28
@kristopherjohnson Kristopher Johnson (kristopherjohnson) changed the title Bump Ditto SDK to 4.14.4-rc.1 across all quickstart apps Bump Ditto SDK to 4.14.4-rc.3 across all quickstart apps Apr 28, 2026
@kristopherjohnson
Copy link
Copy Markdown
Collaborator Author

Superseded by #274 — rebased onto rc.3 (was rc.1).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant