Skip to content

fix: use nanoid/non-secure to avoid unnecessary dependency on crypto #1123

fix: use nanoid/non-secure to avoid unnecessary dependency on crypto

fix: use nanoid/non-secure to avoid unnecessary dependency on crypto #1123

Triggered via pull request March 12, 2026 19:05
Status Success
Total duration 16m 38s
Artifacts

expo.yml

on: pull_request
Install and build
16m 35s
Install and build
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Install and build
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, expo/expo-github-action@v8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Install and build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>07g6zaQAAAAACqYhHToW4TLgZiYP4wxIuQ0hHRURHRTE3MDUARWRnZQ==
Install and build
Failed to restore: Cache service responded with 400