Migration: v2.2 → v2.3
The v2.3 release adds the Flutter plugin (dvai_bridge on pub.dev) to the dvai-bridge family and republishes the Phase 3D Android umbrella AAR at 2.3.0 for build-graph alignment. Existing iOS / Android / React Native consumers see no behaviour changes.
What changed
| Family member | v2.2 → v2.3 change |
|---|---|
@dvai-bridge/capacitor | No source changes — version bumped in lockstep. |
@dvai-bridge/ios | No source changes — SwiftPM/CocoaPods stay at v2.2.x. |
@dvai-bridge/android | Republished at 2.3.0 — no Kotlin source changes. Build-graph alignment with the new Flutter plugin. |
@dvai-bridge/react-native | No source changes — version bumped in lockstep. |
dvai_bridge (Flutter) | New. Pigeon-driven Flutter plugin wrapping iOS + Android SDKs. Published to pub.dev. |
Distribution asymmetry — Flutter is on pub.dev
The Flutter plugin is the only family member published publicly:
| Family member | Distribution | Public/Private |
|---|---|---|
@dvai-bridge/capacitor | npm (GitHub Packages) | private |
@dvai-bridge/ios | SwiftPM (GitHub repo) + CocoaPods (Trunk) | public (CocoaPods) |
@dvai-bridge/android | Maven (GitHub Packages) | private |
@dvai-bridge/react-native | npm (GitHub Packages) | private |
dvai_bridge (Flutter) | pub.dev | public |
Flutter consumers expect packages on pub.dev — there is no first-class private-pub equivalent in the ecosystem. The package code itself is OSS-friendly. The runtime native dependencies (the iOS SwiftPM / pod and the Android AAR) still flow through the family's normal channels — so consumers still need a GitHub PAT for the Android Maven repo even though the Dart package itself is public. See Flutter SDK guide for the settings.gradle.kts snippet.
What action consumers need to take
iOS / Android / React Native consumers
No action required. Bump your dependency to v2.3.0 if you want the republished AAR — otherwise v2.2.x continues to work.
Flutter consumers (new)
flutter pub add dvai_bridgePlus the iOS Podfile + Android settings.gradle.kts snippets in the Flutter SDK guide.
Versioning policy reminder
From v2.0 onward (per the v1.6 → v2.0 migration's policy section):
- Version bumps and git tags happen at whole-phase boundaries. v2.3 is Phase 3F.
- Tag-first, then CHANGELOG entry.
- Breaking-change releases (major bumps) ship with a migration guide in
docs/migration/. v2.3 is additive — no breaking changes.
Pre-existing migrations
Still on v1.6 or earlier? See v1.6 → v2.0 migration first.