Skip to content

Upgrade flutter_secure_storage to ^11.0.0 - #8

Open
Rexios80 wants to merge 1 commit into
mainfrom
cursor/upgrade-flutter-secure-storage-2af3
Open

Upgrade flutter_secure_storage to ^11.0.0#8
Rexios80 wants to merge 1 commit into
mainfrom
cursor/upgrade-flutter-secure-storage-2af3

Conversation

@Rexios80

@Rexios80 Rexios80 commented Sep 8, 2026

Copy link
Copy Markdown
Member

Why

Published oauth_flutter 0.0.12 dropped from 160/160 to 150/160 pub points. Pana’s “Support up-to-date dependencies” check fails because flutter_secure_storage: ^10.0.0 does not allow latest stable 11.0.0.

No other direct dependency is behind its latest stable.

What changed

  • Bump flutter_secure_storage from ^10.0.0 to ^11.0.0.
  • Bump package version to 0.0.13 and add a changelog entry so this is publishable.
  • Update the Android minSdk example in the README from 23 to 24 (flutter_secure_storage 11.0.0 raised its Android minimum).

API check

SecureTokenStorage only uses:

  • FlutterSecureStorage(...)
  • AndroidOptions()
  • IOSOptions(accessibility: KeychainAccessibility.first_unlock)
  • read / write / delete by key

Those APIs are unchanged and still const in 11.0.0. v11 breaking changes (removed deprecated Android ciphers, encryptedSharedPreferences, and sharedPreferencesName) are not used here, so no Dart code changes were required.

Verification

  • flutter pub get resolves flutter_secure_storage 11.0.0
  • dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides shows every direct dependency at Latest
  • dart analyze reports no issues

After publishing 0.0.13, the missing 10 points from “All of the package dependencies are supported in the latest version” should be restored.

Open in Web Open in Cursor 

Restore the lost pub.dev points by allowing the latest stable
flutter_secure_storage. The SecureTokenStorage APIs we use are
unchanged in 11.x; Android minSdk in the README is now 24.

Co-authored-by: Rexios <rexios@rexios.dev>
@Rexios80
Rexios80 marked this pull request as ready for review September 8, 2026 13:09
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.

2 participants