Repository navigation
fix(mobile): pin expo-audio to the patched 57.0.4 - #139
Conversation
Release Smoke regenerates pnpm-lock.yaml from scratch, so every range is re-resolved from the registry. `~57.0.4` now resolves past the version patches/expo-audio@57.0.4.patch targets, and pnpm fails the required check with ERR_PNPM_UNUSED_PATCH on every open PR at once. Same fix as #109 did for expo-sharing: pin the exact patched version. The lockfile diff is only the importer specifier line. Verified by replicating the check — deleting pnpm-lock.yaml and running `vp install --lockfile-only --ignore-scripts` completes with no unused-patch error. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
No major structural issues.
This is a one-line specifier pin (~57.0.4 → 57.0.4) plus the matching lockfile importer line. It aligns the mobile dep with the existing exact expo-audio@57.0.4 patch so Release Smoke’s lockfile regen cannot walk past it. Same shape as #109. No new branching, abstractions, file-size growth, or layer leakage.
Sent by Cursor Automation: Thermo nuke 4.6
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |


What Changed
apps/mobile/package.jsonpinsexpo-audioto57.0.4instead of~57.0.4. The lockfile diff is the one importer specifier line.Why
Release Smoke is a required check and it deletes
pnpm-lock.yamlin a temp copy, then runsvp install --lockfile-only. That re-resolves every range from the registry.pnpm-workspace.yamlpatches the exactexpo-audio@57.0.4, so the moment a newer 57.0.x published, resolution moved past the patched version and pnpm failed with:That turns every open PR red at once with no change on the PR's side — currently blocking #137. Identical shape to #109, which pinned
expo-sharingfor the same reason.Validation
Replicated the check locally: deleted
pnpm-lock.yamland ranvp install --lockfile-only --ignore-scripts, which completes clean with no unused-patch error. With the specifier restored to~57.0.4it fails. An incrementalvp install --lockfile-onlyon top of the hand-edited lockfile makes no further changes and passes supply-chain policy.Note
@react-native-menu/menu(^2.0.0) andreact-native-gesture-handler(~2.32.0) are also patched on ranges, so they will do this too. Not touching them here — one concern per PR.Checklist
Model: Claude Opus 5 (1M context). Harness: Claude Code.
🤖 Generated with Claude Code