chore(deps): bump flutter_secure_storage from 10.3.1 to 11.2.0

[dependabot]

Bumps flutter_secure_storage from 10.3.1 to 11.2.0.

Release notes

Sourced from flutter_secure_storage's releases.

flutter_secure_storage: v11.2.0

11.2.0 (2026-09-16)

Features

• android: requireBiometricsPerOperation flag (#1264) (321cf97)

Bug Fixes

• android: don't hang when biometric negative button is tapped (#1267) (405c6e6)
• android: fix fresh biometric install crash on non-namespaced stores (120bdf4)
• android: port the shared-key multi-instance fixes to v11.x (6cc9ddc)
• android: recover biometric-protected storage on post-auth cipher failure (#1271) (77eed59)
• android: recover the biometric app key on a namespace switch (31f6eeb)
• android: scope deleteAll to the key prefix instead of clearing the file (#1266) (34170b2)
• darwin: find keychain items across accessibility levels (#1269) (9ae0e42)
• don't report pending namespace recovery as data loss in checkUpgradeStatus (f795d52)

flutter_secure_storage: v11.1.1

11.1.1 (2026-09-11)

Bug Fixes

• android: read saved key-cipher marker instead of toString() on a KeyCipher (#1256) (73f0ef5)

flutter_secure_storage: v11.1.0

11.1.0 (2026-09-10)

Features

• add checkUpgradeStatus() to report data lost on a direct major upgrade (#1243) (fc716ea)

Bug Fixes

• android: move wrapped key when switching between sharedPreferencesName and storageNamespace (2482e34)
• android: use flutter.compileSdkVersion (36) instead of pinning compileSdk (37) (#1236) (0530fe7), closes #1224
• require flutter_secure_storage_platform_interface ^2.1.0 for checkUpgradeStatus (#1247) (0d3d6f2)

flutter_secure_storage: v11.0.0

11.0.0 (2026-08-06)

Breaking changes

items deprecated in v10 have been removed. Any data saved using deprecated algorithms or features will be unusable after this upgrade. If you used a version prior to v10, upgrade to v10 first so existing data is migrated.

... (truncated)

Commits

• 805638b chore(develop): release flutter_secure_storage 11.2.0 (#1262)
• 8ccc05f chore(develop): release flutter_secure_storage_darwin 0.4.3 (#1272)
• 3f6fc31 chore(deps): bump org.jetbrains.kotlin.android (#1274)
• 67516e2 chore(develop): release flutter_secure_storage_platform_interface 2.1.1 (#1263)
• 1892db8 docs: add alternative Linux implementations (#1273)
• a6090d8 doc: update badge link
• ca36072 doc: update badge links
• 9ae0e42 fix(darwin): find keychain items across accessibility levels (#1269)
• 77eed59 fix(android): recover biometric-protected storage on post-auth cipher failure...
• 405c6e6 fix(android): don't hang when biometric negative button is tapped (#1267)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, pub. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3a156be

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR