jjbruntonandClaude Opus 5 aa062c9fd0 fix(mobile): make ota-publish actually run under a path with spaces ...

The entrypoint guard compared process.argv[1] against
new URL(import.meta.url).pathname. A URL pathname percent-encodes spaces, so
in any checkout whose absolute path contains one the comparison never matched
and main() never ran.

Every ota:preflight:*, ota:publish:*, and ota:doctor:* script then exited 0
having done absolutely nothing, which is indistinguishable from success. A
publish that silently no-ops is worse than one that fails: it reports a
shipped update that never left the machine.

Compare resolved filesystem paths instead.

Verified from a checkout whose path contains a space: before the change
`node scripts/ota-publish.mjs production --preflight` exited 0 with no
output; after it runs a real export for both platforms and prints the
preflight confirmation. Argument validation still rejects unknown targets and
unsupported EOAS arguments.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-31 11:09:38 +01:00

..

admin

feat(admin): proxy /v1 API calls through the local admin dev server

2026-08-30 20:12:23 +01:00

api

fix(e2e): align browser harness with local stack

2026-08-30 21:00:12 +01:00

mcp

feat(backend): add standalone data plane

2026-08-28 14:42:11 +01:00

mobile

fix(mobile): make ota-publish actually run under a path with spaces

2026-08-31 11:09:38 +01:00

supabase

ci(deploy): establish staged Dokploy promotion

2026-08-28 14:54:12 +01:00

web

security(web): upgrade Next to 15.5.24

2026-08-30 21:14:33 +01:00