Skip to content

fix: re-prompt on invalid sandbox name instead of exiting #2416

fix: re-prompt on invalid sandbox name instead of exiting

fix: re-prompt on invalid sandbox name instead of exiting #2416

Re-run triggered March 31, 2026 23:26
Status Success
Total duration 9m 22s
Artifacts 2

pr.yaml

on: pull_request
sandbox-images-and-e2e  /  build-sandbox-images
5m 36s
sandbox-images-and-e2e / build-sandbox-images
sandbox-images-and-e2e  /  build-sandbox-images-arm64
1m 19s
sandbox-images-and-e2e / build-sandbox-images-arm64
sandbox-images-and-e2e  /  test-e2e-sandbox
1m 10s
sandbox-images-and-e2e / test-e2e-sandbox
sandbox-images-and-e2e  /  test-e2e-gateway-isolation
1m 20s
sandbox-images-and-e2e / test-e2e-gateway-isolation
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
sandbox-images-and-e2e / build-sandbox-images
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
sandbox-images-and-e2e / test-e2e-sandbox
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/
sandbox-images-and-e2e / test-e2e-gateway-isolation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
isolation-image Expired
1.1 GB
sha256:92c3e77c3e560db893506108b83fb3dfaa1242588cb7c883ed0120adb6312136
sandbox-test-image Expired
1.1 GB
sha256:04e3c85c51400babc3c54f126310b9546f457757f2e13f2fb987a2149abb47e8