chore(deps): upgrade expo-secure-store to v55.0.13#224
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Upgrades
expo-secure-storefrom14.2.4→55.0.13(conflict-free replacement for #219).PR #219 was generated by Renovate but had conflicts in
package.jsonandpnpm-lock.yamldue to concurrent merges onmain. This PR applies the same change cleanly on top of the latestmain.Migration analysis
expo-secure-storeswitched to Expo SDK-aligned versioning (v14 → Expo SDK 52, v55 → Expo SDK 55). The large version jump is a versioning scheme change, not 40 breaking iterations.All breaking changes between v14.2.4 and v55.0.13 are platform minimum version bumps only (iOS deployment target, Android SDK target). There are zero JavaScript API changes.
The three methods this codebase uses are unchanged in v55:
setItemAsync(key, value)✅getItemAsync(key)✅deleteItemAsync(key)✅The existing
peerDependenciesrange"expo-secure-store": ">=11.0.0"already covers v55 — no additional changes needed.Changes
package.json: bump dev dependency pin14.2.4→55.0.13pnpm-lock.yaml: regenerated lock fileCloses #219