Expo Dev Build #1259
expo-dev-build.yml
on: workflow_dispatch
Expo dev build (main-dev-expo)
/
...
/
generate-build-version
Expo dev build (main-dev-expo)
/
...
/
bump-version
Matrix: Expo dev build (main-dev-expo) / setup-dependencies
Matrix: Expo dev build (main-dev-expo) / build
Expo dev build (main-dev-expo)
/
Emit build metadata
0s
Annotations
8 errors, 3 warnings, and 2 notices
|
Expo dev build (main-dev-expo) / Setup Dependencies (android) / Setup Node Modules (android)
The run was canceled by @vinnyhoward.
|
|
Expo dev build (main-dev-expo) / Setup Dependencies (android) / Setup Node Modules (android)
The operation was canceled.
|
|
Expo dev build (main-dev-expo) / Setup Dependencies (ios) / Setup Node Modules (ios)
The run was canceled by @vinnyhoward.
|
|
Expo dev build (main-dev-expo) / Setup Dependencies (ios) / Setup Node Modules (ios)
The operation was canceled.
|
|
Expo Dev Build
The run was canceled by @vinnyhoward.
|
|
Expo Dev Build
The run was canceled by @vinnyhoward.
|
|
Expo Dev Build
The run was canceled by @vinnyhoward.
|
|
Expo Dev Build
The run was canceled by @vinnyhoward.
|
|
Expo dev build (main-dev-expo) / prepare
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Expo dev build (main-dev-expo) / Setup Dependencies (android) / Setup Node Modules (android)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Expo dev build (main-dev-expo) / Setup Dependencies (ios) / Setup Node Modules (ios)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08, ruby/setup-ruby@44511735964dcb71245e7e55f72539531f7bc0eb. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Resource Utilization
Peak CPU utilization: 10.03 cores (62.69% of 16.00) at 47s
Peak memory utilization: 4.3 GB (8.44% of 50 GB) at 80s
|
|
Resource Utilization
Peak CPU utilization: 8.00 cores (100.00% of 8.00) at 36s
Peak memory utilization: 10 GB (29.96% of 34 GB) at 51s
|