Skip to content

BridgeJS: Fix for-loop emission in stack codegen #27

BridgeJS: Fix for-loop emission in stack codegen

BridgeJS: Fix for-loop emission in stack codegen #27

Triggered via push April 9, 2026 10:42
Status Failure
Total duration 19m 40s
Artifacts 1

test.yml

on: push
prettier
8s
prettier
format
34s
format
check-bridgejs-generated
2m 49s
check-bridgejs-generated
Matrix: Build for native target
Matrix: Test BridgeJS against Swift versions
Matrix: Build and Test
deploy-examples
4s
deploy-examples
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
check-bridgejs-generated
Process completed with exit code 1.
check-bridgejs-generated
BridgeJS generated files are out of date. Please run `./Utilities/bridge-js-generate.sh` and commit the changes.
deploy-examples
Error: Failed to create deployment (status: 404) with build version 148e65bd4a4fcba720b3327ee4e6799aa5420479. Request ID 5801:1A5D11:DF66F8:38741AA:69D78732 Ensure GitHub Pages has been enabled: https://github.com/PassiveLogic/JavaScriptKit/settings/pages
deploy-examples
HttpError: Not Found at /home/runner/work/_actions/actions/deploy-pages/v5/node_modules/@octokit/request/dist-node/index.js:124:1 at processTicksAndRejections (node:internal/process/task_queues:104:5) at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v5/src/internal/api-client.js:125:1) at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v5/src/internal/deployment.js:73:1) at main (/home/runner/work/_actions/actions/deploy-pages/v5/src/index.js:30:1)
deploy-examples
Creating Pages deployment failed
Build and Test (ubuntu-24.04, https://download.swift.org/swift-6.3-branch/ubuntu2404/swift-6.3-DE...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swiftwasm/setup-swiftwasm@v2. 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/
Build and Test (ubuntu-24.04, https://download.swift.org/development/ubuntu2404/swift-DEVELOPMENT...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swiftwasm/setup-swiftwasm@v2. 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/
Build and Test (ubuntu-22.04, https://download.swift.org/swift-6.1-release/ubuntu2204/swift-6.1-R...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swiftwasm/setup-swiftwasm@v2. 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/
Build and Test (ubuntu-22.04, https://download.swift.org/development/ubuntu2204/swift-DEVELOPMENT...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swiftwasm/setup-swiftwasm@v2. 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/
build-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, swiftwasm/setup-swiftwasm@v2. 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
github-pages
37.1 MB
sha256:4d98aed02c580f282715febcb7b9b5959052400cc7bb016e206bf09d104ebca0