Pin expo-age-range to 0.2.18 so the patch applies
The `^0.2.17` range floated up to 0.2.18 on reinstall, but pnpm matches patchedDependencies by exact version, so the 0.2.17 patch was orphaned (ERR_PNPM_UNUSED_PATCH) and the Swift concurrency fix never applied. Pin to the exact resolved version and move the patch to match; the patch context is identical in 0.2.18, so it applies cleanly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
+1
-1
@@ -20,7 +20,7 @@ allowBuilds:
|
||||
'unrs-resolver': true
|
||||
patchedDependencies:
|
||||
'@sentry/react-native@6.20.0': patches/@sentry__react-native@6.20.0.patch
|
||||
expo-age-range@0.2.17: patches/expo-age-range@0.2.17.patch
|
||||
expo-age-range@0.2.18: patches/expo-age-range@0.2.18.patch
|
||||
'expo-glass-effect@55.0.8': patches/expo-glass-effect@55.0.8.patch
|
||||
'expo-haptics@15.0.8': patches/expo-haptics@15.0.8.patch
|
||||
'expo-image-picker@17.0.11': patches/expo-image-picker@17.0.11.patch
|
||||
|
||||
Reference in New Issue
Block a user