Dependabot pushes in-repo branches, so its PRs pass the fork guard and the
per-PR OTA job runs — but GitHub withholds repo secrets from Dependabot-
triggered runs, so EXPO_TOKEN is empty and the job fails at "Setup Expo
project". Result: a red check on every dependabot PR (fails closed, nothing
reaches AWS, but it's noise on an unrelated PR).
Exclude bot authors via user.type. This keeps the fork guard as the trust
boundary and does not reintroduce the author_association check, which
wrongly skipped private org members' PRs.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* use xlarge runner for macos build
* try and fix yarn cache
* update actions/cache for pods step
* use expo github action main rather than v8
* update all actions to the same
* use yarn cache where missing
* use custom github action for fingerprinting
* update pr workflow
* update names of workflows
* make a native change (testing)
* adjust the action
* Revert "make a native change (testing)"
This reverts commit 8db9835733.
* update bundle-deploy script
* test a prod build
* crazy depth
* manually set
* use prod default
* force prod
* revert test changes
* save cache after deploy
* revert testing
* simplify list logic further
more simplification
simplify by removing `isEmpty`
use `isFetchingNextPage` everywhere for clarity
change `isFetching` to `isFetchingNextPage` for clarity
remove some useless `useMemo`s
move `renderItem` and `keyExtractor` out of component
* clean bundle size check
* update deploy
* adjust
* adjust
* one test
* try now
* test it
* done
try that again 9
try that again 8
try that again 7
try that again 6
try that again 5
try that again 4
try that again 3
try that again 2
try that again
merge base 3
merge base 2
merge base
use latest main commit rather than tag
webpack diff analyzer
use cache v4
use cache
again...
blegh
blegh
try cache again
cache
try again
one more adjutment
adjust
okay again maybe
maybe now?
maybe now
oops again
oops
add diff comments
add open analyzer script
add webpack analyzer