Allow flutter_secure_storage v10 (widen constraint)#6
Merged
Conversation
Widen the flutter_secure_storage constraint from ^9.2.0 to >=9.2.0 <11.0.0 so consumers can adopt v10 while v9 stays supported. v10 only touches the API surface escalated uses (const FlutterSecureStorage() + read/write/delete with key:/value:) via unchanged method signatures, so no code changes are needed; verified with analyzer (0 errors) and the test suite against 10.3.1. v10 raises platform minimums, so bump the package environment to Dart 3.3.0 / Flutter 3.19.0 to match. Consuming apps must also target Android minSdk 23 and iOS 12.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Widens
flutter_secure_storagefrom^9.2.0to>=9.2.0 <11.0.0so consumers (e.g. the HaulOy customer app's release-prep line) can move to v10 while v9 stays supported.Why safe: escalated only uses
const FlutterSecureStorage()+read/write/delete(key:/value:) intheme_provider.dartandservices/auth_hooks.dart. v10 leaves those method signatures unchanged, so no Dart code changes are needed. Verified:flutter analyze→ 0 errors and the test suite passes againstflutter_secure_storage 10.3.1.Also bumped
environmentto Dart3.3.0/ Flutter3.19.0to match v10's minimums. Consuming apps must target Android minSdk 23 and iOS 12 (v10 requirements).v10's Android default cipher changed but auto-migrates existing data (
migrateOnAlgorithmChange: true); worst case is a one-time token re-fetch.