I’m targeting Flutter 3.44.9 with Dart 3.12.2 and Swift Package Manager enabled.
I understand that changing the dependency directly to:
flutter_fgbg: ^0.8.0
would require Dart 3.8+ and drop support for older Flutter versions.
Could the constraint instead be widened to support both releases?
flutter_fgbg: ">=0.7.1 <0.9.0"
Pub should then resolve:
- flutter_fgbg 0.8.0 on Dart 3.8+, enabling SPM support.
- A compatible 0.7.x release on older Dart SDKs, preserving existing Flutter support.
Verification
I tested the Segment SPM branch at commit 3b99caf with:
dependency_overrides:
flutter_fgbg: 0.8.0
On Flutter 3.44.9:
- flutter_fgbg disappeared from the SPM warning.
- Both segment_analytics and flutter_fgbg were integrated through SwiftPM.
Requested outcome
Please consider widening the dependency range and testing resolution against both the current minimum Dart SDK and Dart 3.8+. This should allow newer applications to use SPM without requiring an immediate minimum Flutter version increase for all users.
I’m targeting Flutter 3.44.9 with Dart 3.12.2 and Swift Package Manager enabled.
I understand that changing the dependency directly to:
flutter_fgbg: ^0.8.0
would require Dart 3.8+ and drop support for older Flutter versions.
Could the constraint instead be widened to support both releases?
flutter_fgbg: ">=0.7.1 <0.9.0"
Pub should then resolve:
Verification
I tested the Segment SPM branch at commit 3b99caf with:
dependency_overrides:
flutter_fgbg: 0.8.0
On Flutter 3.44.9:
Requested outcome
Please consider widening the dependency range and testing resolution against both the current minimum Dart SDK and Dart 3.8+. This should allow newer applications to use SPM without requiring an immediate minimum Flutter version increase for all users.