Files

T

Claude fbcd5422ee Build PR OTA bundle in parallel with the fingerprint check

publish-pr-ota needed fingerprint-native, so the bundle build - the slow
half - did not start until the fingerprint had finished, even though the
bundle does not depend on the fingerprint verdict. Only the decision to
publish it does.

Split the job in two: build-pr-ota builds and assembles the bundle with no
dependency on the fingerprint (so it runs alongside it) and hands it over
as a short-lived artifact, and publish-pr-ota keeps the fingerprint gate
and does just the denis publish. A dirty fingerprint now discards an
already-built bundle instead of saving the build, which costs a runner but
takes the fingerprint's wall clock off the critical path of every
fingerprint-clean PR.

Since the build job already has the EAS CLI set up, it also reads the
native build numbers and exposes them (along with the release version) as
job outputs, so the publish job needs neither EXPO_TOKEN nor node_modules
and can invoke denisPublish.sh directly rather than through the
use-build-number wrapper. denisPublish.sh gains SKIP_BUNDLE_ASSEMBLY for
that case, where bundleTempDir arrives as an artifact and ./dist is not
present; without it the script assembles the directory as before, so the
main-branch deploy is unaffected.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UL83tcSq9MvwBkUGJGRyWV

2026-07-30 15:55:56 +00:00

push-notification

Migrate from Yarn 1 to pnpm (#10465 )

2026-05-18 09:51:04 -07:00

buildAndroidRelease.sh

React Native New Arch (#10980 )

2026-07-23 18:25:40 +03:00

bundleUpdate.js

disable new arch (#8561 )

2025-06-23 10:11:17 -07:00

bundleUpdate.sh

Publish one bundle version to both OTA origins, not two (#11291 )