Pin expo-age-range to 0.2.18 so the patch applies

Browse Source

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:

Eric Bailey

2026-06-29 19:37:52 -05:00

parent 369cf5edd3

commit 5d2359ef6c

4 changed files with 8 additions and 8 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

patches/expo-age-range@0.2.17.patch → patches/expo-age-range@0.2.18.patch