[wit-parser] Migrate to structured errors in the AST/package parser #6396
PhoebeSzmucermain.yml
on: pull_request
Matrix: Build wasm-tools
Matrix: Test
Matrix: Test the C API
Test (no-hash-maps)
3m 29s
Test with extra Cargo features
2m 17s
Test libdl.so
1m 11s
Test on WebAssembly
3m 28s
Rustfmt
26s
Fuzz
2m 36s
check
3m 15s
Check generated files are up-to-date
1m 18s
doc
3m 28s
clippy
2m 55s
verify-publish
2m 52s
maybe-trigger-tag
0s
Annotations
31 errors and 32 warnings
|
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
|
|
Test (macos-latest, stable)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
check
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
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.
|
|
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 (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.
|
|
Test on WebAssembly
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test on WebAssembly
The operation was canceled.
|
|
Test (ubuntu-latest, nightly-2026-01-20)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
doc
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, nightly-2026-01-20)
The operation was canceled.
|
|
doc
The operation was canceled.
|
|
Test (ubuntu-latest, stable, 1)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (ubuntu-latest, stable, 1)
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.
|
|
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.
|
|
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.
|
|
Test (no-hash-maps)
Canceling since a higher priority waiting request for CI-refs/pull/2465/merge exists
|
|
Test (no-hash-maps)
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.
|
|
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/
|
|
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/
|
|
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/
|
|
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/
|
|
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: actions/upload-artifact@v4, 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/
|
|
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: actions/upload-artifact@v4, 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/
|
|
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: actions/upload-artifact@v4, 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: actions/upload-artifact@v4, 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/
|
|
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/
|
|
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 (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: actions/upload-artifact@v4, 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: actions/upload-artifact@v4, 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: actions/upload-artifact@v4, 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: actions/upload-artifact@v4, 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/
|
|
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 (windows-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/
|
|
Build wasm-tools (x86_64-windows, windows-latest, x86_64-pc-windows-msvc, -Ctarget-feature=+crt-s...
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 (windows-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 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/
|
|
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/
|
|
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/
|
|
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/
|
|
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, 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/
|
|
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/
|
|
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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
bins-aarch64-linux
|
5.52 MB |
sha256:a4286e084e55eb9d8dd5317d284bcefabe2092fde2a52682c32ee5e014fd41ae
|
|
|
bins-aarch64-macos
|
4.98 MB |
sha256:d9f7806473d6a7c6c5699d783d7b22ef74b61bf8b83cb53b09e34701a0480d85
|
|
|
bins-aarch64-musl
|
5.58 MB |
sha256:7f37aae2e6c120afffbd20069c62dcf401966226750f43d3870b7ea303a15f4a
|
|
|
bins-riscv64-linux
|
5.89 MB |
sha256:226d312f402f917bd373313cc3962d1b644d9df08d1705c1ff5e04e90e51b785
|
|
|
bins-wasm32-wasip1
|
3.57 MB |
sha256:82c996c42238709ae9fa8e9fc2ad3930e7dbad0d0115ed393e3fdba51188e775
|
|
|
bins-x86_64-linux
|
5.57 MB |
sha256:c102da9cbaf5ad5e708ebe9f012bffe11b0680ba683c1446483ba7f3afbd2c25
|
|
|
bins-x86_64-macos
|
5.38 MB |
sha256:23aea58d51b594b87426ed77f422a69d49d62ea31d26ed2925f8fddf0d7a8910
|
|
|
bins-x86_64-musl
|
5.81 MB |
sha256:963a8c268c1f84d4a42b0f7939d6a09c7fcc0ff647b33cfdd8183fcab3a1e654
|
|