Skip to content

Revert "BridgeJS: Correctly emit @JS methods in extensions" #2487

Revert "BridgeJS: Correctly emit @JS methods in extensions"

Revert "BridgeJS: Correctly emit @JS methods in extensions" #2487

Triggered via pull request March 16, 2026 21:34
Status Success
Total duration 19m 55s
Artifacts 1

test.yml

on: pull_request
prettier
7s
prettier
format
37s
format
check-bridgejs-generated
2m 34s
check-bridgejs-generated
Matrix: Build for native target
Matrix: Test BridgeJS against Swift versions
Matrix: Build and Test
deploy-examples
0s
deploy-examples
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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/

Artifacts

Produced during runtime
Name Size Digest
github-pages Expired
37.1 MB
sha256:9ab393319916f60aca50052b982e1335fae92ccd9d2d0cf6e3675df0c2f2bdda