Skip to content

fix(core): Lazy-load Metro internal modules to prevent Expo 55 import errors #12852

fix(core): Lazy-load Metro internal modules to prevent Expo 55 import errors

fix(core): Lazy-load Metro internal modules to prevent Expo 55 import errors #12852

Re-run triggered April 7, 2026 07:36
Status Success
Total duration 6m 16s
Artifacts 6

sample-application.yml

on: pull_request
Ready-to-merge gate  /  Missing "ready-to-merge" label
3s
Ready-to-merge gate / Missing "ready-to-merge" label
diff_check  /  diff_check
11s
diff_check / diff_check
detect-changes  /  Detect file changes
5s
detect-changes / Detect file changes
Matrix: build-android
Matrix: build-ios
Matrix: build-macos
Test android production REV2
6m 13s
Test android production REV2
Test ios production REV2
6m 1s
Test ios production REV2
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 1 notice
Test ios production REV2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dniHze/maestro-test-action@bda8a93211c86d0a05b7a4597c5ad134566fbde4, futureware-tech/simulator-action@e89aa8f93d3aec35083ff49d2854d07f7186f7f5. 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: 4.00 cores (100.00% of 4.00) at 54s Peak memory utilization: 11 GB (62.12% of 17 GB) at 300s