Skip to content

chore: update Customer.io Android SDK to 4.19.0#360

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
auto-update/native-sdks-20260702-100443
Open

chore: update Customer.io Android SDK to 4.19.0#360
github-actions[bot] wants to merge 1 commit into
mainfrom
auto-update/native-sdks-20260702-100443

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Automated update of Customer.io native SDK dependencies:

Key Changes

Android SDK 4.19.0

4.19.0 (2026-07-01)

Testing

  • ✅ Flutter analysis passed
  • ✅ Unit tests passed
  • ✅ iOS compilation verified
  • ✅ Android compilation verified
  • ✅ Sample app builds successfully

Migration Notes

This update maintains API compatibility. Please test your integration thoroughly and review the release notes linked above for any specific changes that might affect your implementation.


🤖 This PR was automatically generated and tested


Note

Medium Risk
Native SDK bumps can change messaging, analytics, and push behavior even when the Flutter API is unchanged; risk is moderate because only the Android pin moves and sample locks were regenerated.

Overview
Bumps the Flutter plugin’s Android Customer.io native dependency from 4.18.2 to 4.19.0 by updating cioVersion in android/build.gradle, so all io.customer.android:* artifacts (datapipelines, push FCM, in-app, and optional location) resolve to the new release.

The CocoaPods and SPM sample apps’ pubspec.lock files are refreshed after pub get: the local customer_io path dependency is recorded as 4.1.2 (was 4.0.0), with matching transitive package bumps and a Dart SDK constraint of >=3.10.0-0 <4.0.0 in the lockfiles.

Reviewed by Cursor Bugbot for commit 34cec05. Bugbot is set up for automated code reviews on this repo. Configure here.

- iOS: 4.5.3 → 4.5.3
- Android: 4.18.2 → 4.19.0

🤖 Automated update with compilation verification
@github-actions github-actions Bot requested a review from a team as a code owner July 2, 2026 10:06
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