chore: flutter support for android 15+ changes

[ChiragAgg5k]

• 🐛 Bug Report: update device_info_plus to 12.0.0 sdk-for-flutter#278

Summary by CodeRabbit

• Chores
  • Updated dependency version constraints to refine compatibility management for Flutter packages.

[coderabbitai]

Walkthrough

This change updates version constraints for two Flutter dependencies in a Pubspec template file. The device_info_plus dependency constraint was modified from ^11.5.0 to >=11.5.0 <13.0.0, and the package_info_plus constraint was updated from ^8.0.2 to >=8.0.2 <10.0.0. Both changes replace caret constraints with explicit range notation, effectively establishing upper bounds on allowed versions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file affected with homogeneous, repetitive changes
• Version constraint syntax updates only; no logic or structural modifications
• Straightforward dependency management adjustments requiring minimal contextual review

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "chore: flutter support for android 15+ changes" is partially related to the changeset. The title conveys the objective and context of the changes (enabling Android 15+ support in the Flutter SDK), which aligns with the referenced issue. However, the actual technical change—updating version constraints for device_info_plus and package_info_plus dependencies—is not explicitly captured in the title. That said, the title is clear and specific enough for a teammate scanning the history to understand the PR is addressing Android 15+ compatibility concerns in the Flutter integration, even if the specific implementation details would require examining the commit.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-update-device_info_plus

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b4a2fd9 and 24e5082.

📒 Files selected for processing (1)

• templates/flutter/pubspec.yaml.twig (1 hunks)

🔇 Additional comments (2)

templates/flutter/pubspec.yaml.twig (2)

25-25: I need to check whether device_info_plus requires package_info_plus v9.x or if there are other dependencies involved.

Let me check the actual PR context and template file to understand the full picture.

Confirm whether package_info_plus v9.x is actually required for this change.

device_info_plus v9.0.0 includes breaking Android build config changes, and package_info_plus v8.0.1 addressed Android 15 nullability handling. The constraint change from ^8.0.2 (allows 8.x) to >=8.0.2 <10.0.0 (allows 9.x) introduces breaking changes unrelated to Android 15 support.

Since v8.0.1 handles nullability on Android 15 and device_info_plus doesn't depend on a specific package_info_plus version, clarify:

• Is v9.x required for compatibility with the updated device_info_plus?
• Or is this constraint overly permissive for future-proofing without immediate need?

---

22-22: Constraint expansion verified as appropriate for Android 15+ support.

Both packages have been updated to support Android 15+ with new build configuration requirements (Android Gradle Plugin >=8.12.1, Gradle >=8.13, Kotlin 2.2.0). The expanded constraints are correct:

• device_info_plus: >=11.5.0 <13.0.0 — includes v12.0.0 with Android 15+ support
• package_info_plus: >=8.0.2 <10.0.0 — includes v9.0.0 with Android 15+ support

The breaking changes in these versions are build configuration updates, not API removals that impact the generated SDK.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}