Skip to content

BridgeJS: Fix name collision for same-named nested structs #2629

BridgeJS: Fix name collision for same-named nested structs

BridgeJS: Fix name collision for same-named nested structs #2629

Triggered via pull request May 11, 2026 16:02
Status Cancelled
Total duration 6m 20s
Artifacts

test.yml

on: pull_request
build-examples
6m 9s
build-examples
prettier
8s
prettier
format
32s
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
deploy-examples
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 5 warnings
build-examples
Canceling since a higher priority waiting request for Run unit tests / 744/merge exists
build-examples
The operation was canceled.
Build and Test (ubuntu-22.04, https://download.swift.org/swift-6.1-release/ubuntu2204/swift-6.1-R...
Canceling since a higher priority waiting request for Run unit tests / 744/merge exists
Build and Test (ubuntu-24.04, https://download.swift.org/swift-6.3-branch/ubuntu2404/swift-6.3-DE...
Canceling since a higher priority waiting request for Run unit tests / 744/merge exists
Build and Test (ubuntu-24.04, https://download.swift.org/development/ubuntu2404/swift-DEVELOPMENT...
Canceling since a higher priority waiting request for Run unit tests / 744/merge exists
Build and Test (ubuntu-22.04, https://download.swift.org/development/ubuntu2204/swift-DEVELOPMENT...
Canceling since a higher priority waiting request for Run unit tests / 744/merge exists
Run unit tests
Canceling since a higher priority waiting request for Run unit tests / 744/merge exists
build-examples
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-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/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/