[wit-parser] Migrate to structured errors in the AST/package parser #6398
PhoebeSzmucermain.yml
on: pull_request
Matrix: Build wasm-tools
Matrix: Test
Matrix: Test the C API
Test (no-hash-maps)
1m 19s
Test with extra Cargo features
1m 12s
Test libdl.so
1m 18s
Test on WebAssembly
1m 18s
Rustfmt
30s
Fuzz
1m 18s
check
1m 6s
Check generated files are up-to-date
1m 19s
doc
1m 17s
clippy
1m 19s
verify-publish
1m 18s
maybe-trigger-tag
Annotations
66 errors and 29 warnings
|
check
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
check
The operation was canceled.
|
|
Test the C API (ubuntu-latest)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test the C API (ubuntu-latest)
The operation was canceled.
|
|
Test (windows-latest, stable)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (windows-latest, stable)
The operation was canceled.
|
|
Build wasm-tools (x86_64-windows, windows-latest, x86_64-pc-windows-msvc, -Ctarget-feature=+crt-s...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (x86_64-windows, windows-latest, x86_64-pc-windows-msvc, -Ctarget-feature=+crt-s...
The operation was canceled.
|
|
Test the C API (macos-latest)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test the C API (macos-latest)
The operation was canceled.
|
|
Test with extra Cargo features
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test with extra Cargo features
The operation was canceled.
|
|
Test libdl.so
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test libdl.so
The operation was canceled.
|
|
doc
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
doc
The operation was canceled.
|
|
Build wasm-tools (x86_64-linux, ubuntu-latest, x86_64-unknown-linux-gnu, ./ci/docker/x86_64-linux...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (x86_64-linux, ubuntu-latest, x86_64-unknown-linux-gnu, ./ci/docker/x86_64-linux...
The operation was canceled.
|
|
Test the C API (windows-latest)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test the C API (windows-latest)
The operation was canceled.
|
|
Test (ubuntu-latest, beta)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, beta)
The operation was canceled.
|
|
verify-publish
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
verify-publish
The operation was canceled.
|
|
Test on WebAssembly
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test on WebAssembly
The operation was canceled.
|
|
Fuzz
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (no-hash-maps)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Fuzz
The operation was canceled.
|
|
Test (no-hash-maps)
The operation was canceled.
|
|
clippy
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
clippy
The operation was canceled.
|
|
Build wasm-tools (x86_64-musl, ubuntu-latest, x86_64-unknown-linux-musl, ./ci/docker/x86_64-musl/...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (x86_64-musl, ubuntu-latest, x86_64-unknown-linux-musl, ./ci/docker/x86_64-musl/...
The operation was canceled.
|
|
Build wasm-tools (aarch64-linux, ubuntu-latest, aarch64-unknown-linux-gnu, ./ci/docker/aarch64-li...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (aarch64-linux, ubuntu-latest, aarch64-unknown-linux-gnu, ./ci/docker/aarch64-li...
The operation was canceled.
|
|
Test (ubuntu-latest, nightly-2025-07-16)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, nightly-2025-07-16)
The operation was canceled.
|
|
Test (ubuntu-latest, msrv, --exclude fuzz-stats --exclude wit-component --exclude wasm-mutate-sta...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (riscv64-linux, ubuntu-latest, riscv64gc-unknown-linux-gnu, ./ci/docker/riscv64-...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, nightly-2026-01-20)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, msrv, --exclude fuzz-stats --exclude wit-component --exclude wasm-mutate-sta...
The operation was canceled.
|
|
Build wasm-tools (riscv64-linux, ubuntu-latest, riscv64gc-unknown-linux-gnu, ./ci/docker/riscv64-...
The operation was canceled.
|
|
Test (ubuntu-latest, nightly-2026-01-20)
The operation was canceled.
|
|
Build wasm-tools (aarch64-windows, windows-11-arm, aarch64-pc-windows-msvc, -Ctarget-feature=+crt...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (aarch64-windows, windows-11-arm, aarch64-pc-windows-msvc, -Ctarget-feature=+crt...
The operation was canceled.
|
|
Build wasm-tools (wasm32-wasip1, ubuntu-latest, wasm32-wasip1)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (wasm32-wasip1, ubuntu-latest, wasm32-wasip1)
The operation was canceled.
|
|
Test (ubuntu-latest, stable, 1)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Check generated files are up-to-date
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, stable, 1)
The operation was canceled.
|
|
Check generated files are up-to-date
The operation was canceled.
|
|
Test (ubuntu-latest, stable)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, stable)
The operation was canceled.
|
|
Test (ubuntu-latest, stable, --cfg=debug_check_try_op, -F wasmparser/try-op)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, stable, --cfg=debug_check_try_op, -F wasmparser/try-op)
The operation was canceled.
|
|
Build wasm-tools (aarch64-musl, ubuntu-latest, aarch64-unknown-linux-musl, ./ci/docker/aarch64-mu...
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (aarch64-musl, ubuntu-latest, aarch64-unknown-linux-musl, ./ci/docker/aarch64-mu...
The operation was canceled.
|
|
Build wasm-tools (aarch64-macos, macos-latest, aarch64-apple-darwin, 10.12)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (aarch64-macos, macos-latest, aarch64-apple-darwin, 10.12)
The operation was canceled.
|
|
Test (macos-latest, stable)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (macos-latest, stable)
The operation was canceled.
|
|
Build wasm-tools (x86_64-macos, macos-latest, x86_64-apple-darwin, 10.12)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Build wasm-tools (x86_64-macos, macos-latest, x86_64-apple-darwin, 10.12)
The operation was canceled.
|
|
Record the result of testing and building steps
Process completed with exit code 1.
|
|
CI
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Rustfmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test the C API (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test the C API (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test with extra Cargo features
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test libdl.so
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
doc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (x86_64-linux, ubuntu-latest, x86_64-unknown-linux-gnu, ./ci/docker/x86_64-linux...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (ubuntu-latest, beta)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
verify-publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test on WebAssembly
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Fuzz
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (no-hash-maps)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (x86_64-musl, ubuntu-latest, x86_64-unknown-linux-musl, ./ci/docker/x86_64-musl/...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (aarch64-linux, ubuntu-latest, aarch64-unknown-linux-gnu, ./ci/docker/aarch64-li...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (ubuntu-latest, nightly-2025-07-16)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (ubuntu-latest, msrv, --exclude fuzz-stats --exclude wit-component --exclude wasm-mutate-sta...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (riscv64-linux, ubuntu-latest, riscv64gc-unknown-linux-gnu, ./ci/docker/riscv64-...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (ubuntu-latest, nightly-2026-01-20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (wasm32-wasip1, ubuntu-latest, wasm32-wasip1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (ubuntu-latest, stable, 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Check generated files are up-to-date
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (ubuntu-latest, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (ubuntu-latest, stable, --cfg=debug_check_try_op, -F wasmparser/try-op)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (aarch64-musl, ubuntu-latest, aarch64-unknown-linux-musl, ./ci/docker/aarch64-mu...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (aarch64-macos, macos-latest, aarch64-apple-darwin, 10.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|
|
Test (macos-latest, stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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 wasm-tools (x86_64-macos, macos-latest, x86_64-apple-darwin, 10.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bytecodealliance/actions/wasmtime/setup@v1. 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/
|