Mobile: stop package.json scripts changing the runtime fingerprint
Status summary: done and locally verified. One config file plus the re-landed update:preview fixes that the fingerprint gotcha forced out of PR #2410.
The expo-updates fingerprint runtime policy hashed package.json scripts: editing update:preview on PR #2410 moved the fingerprint from 37fb004c to f195c3d2, which would have stranded every installed binary on stale JS despite zero native changes.
- add
apps/mobile/fingerprint.config.jswithsourceSkips: ["PackageJsonScriptsAll"]scripts never ship in the bundle; deps still count - verify a scripts-only edit no longer changes the hash
expo-updates fingerprint:generate→1bf9f0fewith and without a script edit - re-land the
update:previewfixes reverted from #2410--message "$(git log -1 --format=%s)"(eas requires --message when non-interactive) and--clear-cache(Metro's shared cache leaks absolute paths across worktrees — see #2410's task notes)
Implementation notes#
- Landing this changes the fingerprint once (
37fb004c→1bf9f0fe-ish as computed on merge): the merge-to-main workflow will detect no matching preview build and auto-trigger one — Misha reinstalls one more time, then script edits are permanently fingerprint-neutral.