Skip to content

BridgeJS: Use shared decodeString for JSTypedClosure error path (#696) #23

BridgeJS: Use shared decodeString for JSTypedClosure error path (#696)

BridgeJS: Use shared decodeString for JSTypedClosure error path (#696) #23

Triggered via push March 11, 2026 01:06
Status Failure
Total duration 19m 34s
Artifacts 1

test.yml

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

Annotations

3 errors and 6 warnings
deploy-examples
Error: Failed to create deployment (status: 404) with build version 7dd02633cb57d4dc9b43328e2cef8ab1407ff7aa. Request ID 0420:25C7C4:157303C:5C245B7:69B0C4B6 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/v4/node_modules/@octokit/request/dist-node/index.js:124:1 at processTicksAndRejections (node:internal/process/task_queues:95:5) at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/api-client.js:125:1) at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/deployment.js:74:1) at main (/home/runner/work/_actions/actions/deploy-pages/v4/src/index.js:30:1)
deploy-examples
Creating Pages deployment failed
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. 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/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. 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. 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. 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. 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/
deploy-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/deploy-pages@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
github-pages
37 MB
sha256:e5c4b2be99199386164ba79ad59627504aed4da086ca81c1843c4f63a26448c2