Update dependency react-native-keychain to v10 #7293
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.
This PR contains the following updates:
8.2.0
->10.0.0
Release Notes
oblador/react-native-keychain (react-native-keychain)
v10.0.0
Compare Source
New features
Breaking Changes & How to Update:
Ensure your
minAndroidSdk
is set to 23 or higher.If your app was using library warmup, simply remove it—autolinking will handle initialization automatically.
If you are using the deprecated and no longer maintained FacebookConceal, consider staying on version 9.x until all users are migrated to a different cipher.
You can use automatic migration with:
Bug fixes
react-native
resolution approach in monorepos by @bakoushin in https://github.com/oblador/react-native-keychain/pull/714Improvements
New Contributors
Full Changelog: oblador/react-native-keychain@v9.2.3...v10.0.0
v9.2.3
Compare Source
Bug fixes
Improvements
New Contributors
Full Changelog: oblador/react-native-keychain@v9.2.2...v9.2.3
v9.2.2
Compare Source
Bug fixes
Improvements
Full Changelog: oblador/react-native-keychain@v9.2.1...v9.2.2
v9.2.1
Compare Source
Bug fixes
New Contributors
Full Changelog: oblador/react-native-keychain@v9.2.0...v9.2.1
v9.2.0
Compare Source
New features
SharedPreferences
with JetpackDataStore
by @ovitrif in https://github.com/oblador/react-native-keychain/pull/629Enhanced security and performance using Google's recommended DataStore solution with seamless migration from existing SharedPreferences. For more details, see Jetpack DataStore documentation
AES-GCM provides stronger security than AES-CBC (now deprecated). Supports both biometric and non-biometric authentication modes
Improvements
New Contributors
Full Changelog: oblador/react-native-keychain@v9.1.0...v9.2.0
v9.1.0
Compare Source
New features
Bug fixes
Improvements
New Contributors
Full Changelog: oblador/react-native-keychain@v9.0.0...v9.1.0
v9.0.0
: 9.0.0Compare Source
New features
Bug fixes
Improvements
Breaking changes
New Contributors
Full Changelog: oblador/react-native-keychain@v8.2.0...v9.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.