Fix open FDs becoming inaccessible after an unlink operation in memfs #2
Arshia001test.yaml
on: pull_request
Set up
3s
Code lint
1m 52s
cargo-deny
15m 13s
NodeJS
33s
Wasi-fyi
33s
WASIX
1m 12s
JSC
15m 48s
Build docs.rs
17m 0s
Matrix: build_linux_riscv64
Matrix: test_interpreter_api
Matrix: build
Matrix: test
Annotations
74 errors and 71 warnings
|
Wasi-fyi
Process completed with exit code 1.
|
|
NodeJS
Process completed with exit code 1.
|
|
WASIX
Process completed with exit code 22.
|
|
CLI integ. tests - linux-arm64
Process completed with exit code 22.
|
|
C-API - linux-riscv64
Process completed with exit code 1.
|
|
Code lint
Process completed with exit code 2.
|
|
WAST (all comp.) - linux-x64
Process completed with exit code 22.
|
|
WAST (all comp.) - linux-arm64
Process completed with exit code 22.
|
|
Singlepass - no-std - linux-musl
Process completed with exit code 22.
|
|
Wasmer-cli - linux-arm64
Process completed with exit code 22.
|
|
C-API - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
WAST (all comp.) - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Cranelift - no-std - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Packages - std - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API with V8 - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Examples - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API with V8 - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
CLI integ. tests - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Examples - linux-arm64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
CLI integ. tests - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
WAST (all comp.) - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Singlepass - no-std - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer-cli binary - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer-cli binary - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer API (sys) - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Singlepass - no-std - linux-arm64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Cranelift - no-std - linux-arm64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Packages - std - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
CLI integ. tests - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer API (sys) - windows-gnu
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Examples - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer-cli - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API with V8 - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API with V8 - windows-x64
The operation was canceled.
|
|
Wasmer-cli - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer-cli - linux-musl
The operation was canceled.
|
|
WAST tests - linux-riscv64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
WAST tests - linux-riscv64
The operation was canceled.
|
|
C-API - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API - linux-x64
The operation was canceled.
|
|
API (sys) - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
API (sys) - windows-x64
The operation was canceled.
|
|
Singlepass - no-std - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Singlepass - no-std - linux-x64
The operation was canceled.
|
|
Wasmer-cli binary - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer-cli binary - linux-x64
The operation was canceled.
|
|
Wasmer-cli binary - linux-arm64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer-cli binary - linux-arm64
The operation was canceled.
|
|
Cranelift - no-std - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Cranelift - no-std - linux-x64
The operation was canceled.
|
|
Packages - std - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Packages - std - windows-x64
The operation was canceled.
|
|
Wasmer-cli - linux-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API - linux-arm64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Wasmer-cli - linux-x64
The operation was canceled.
|
|
C-API - linux-arm64
The operation was canceled.
|
|
C-API - windows-gnu
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API - windows-gnu
The operation was canceled.
|
|
Packages - std - linux-arm64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Packages - std - linux-arm64
The operation was canceled.
|
|
API (sys) - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
API (sys) - linux-musl
The operation was canceled.
|
|
C-API with V8 - windows-gnu
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
C-API with V8 - windows-gnu
The operation was canceled.
|
|
Examples - linux-musl
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Examples - linux-musl
The operation was canceled.
|
|
API (sys) - windows-gnu
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
API (sys) - windows-gnu
The operation was canceled.
|
|
Cranelift - no-std - windows-x64
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Cranelift - no-std - windows-x64
The operation was canceled.
|
|
Build docs.rs
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
Build docs.rs
The operation was canceled.
|
|
test-sys
Canceling since a higher priority waiting request for test-sys-refs/pull/1/merge exists
|
|
NodeJS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. 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/
|
|
Code lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Code lint
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Code lint
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer API (sys) - windows-x64
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, ilammy/msvc-dev-cmd@v1, whywaita/actions-cache-s3@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/
|
|
Wasmer API (sys) - windows-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer API (sys) - windows-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer API (sys) - linux-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, whywaita/actions-cache-s3@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/
|
|
Wasmer API (sys) - linux-musl
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer API (sys) - linux-musl
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API with V8 - linux-arm64
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, whywaita/actions-cache-s3@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/
|
|
C-API with V8 - linux-arm64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API with V8 - linux-arm64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer API (sys) - linux-arm64
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, whywaita/actions-cache-s3@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/
|
|
Wasmer API (sys) - linux-arm64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer API (sys) - linux-arm64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - linux-x64
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, whywaita/actions-cache-s3@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/
|
|
API (sys) - linux-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - linux-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - linux-arm64
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, whywaita/actions-cache-s3@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/
|
|
API (sys) - linux-arm64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - linux-arm64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli binary - windows-gnu
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, whywaita/actions-cache-s3@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/
|
|
Wasmer-cli binary - windows-gnu
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli binary - windows-gnu
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
cargo-deny
Docker build failed with exit code 1, back off 5.791 seconds before retry.
|
|
JSC
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, whywaita/actions-cache-s3@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/
|
|
JSC
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
JSC
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API - linux-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
C-API - linux-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API - linux-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - windows-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1, whywaita/actions-cache-s3@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/
|
|
API (sys) - windows-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - windows-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Singlepass - no-std - linux-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Singlepass - no-std - linux-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Singlepass - no-std - linux-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli binary - linux-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Wasmer-cli binary - linux-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli binary - linux-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli binary - linux-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Wasmer-cli binary - linux-arm64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli binary - linux-arm64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Cranelift - no-std - linux-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Cranelift - no-std - linux-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Cranelift - no-std - linux-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Packages - std - windows-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1, whywaita/actions-cache-s3@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/
|
|
Packages - std - windows-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Packages - std - windows-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli - linux-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
C-API - linux-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Wasmer-cli - linux-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API - linux-arm64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Wasmer-cli - linux-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API - linux-arm64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API - windows-gnu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
C-API - windows-gnu
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
C-API - windows-gnu
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Packages - std - linux-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Packages - std - linux-arm64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Packages - std - linux-arm64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
API (sys) - linux-musl
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
API (sys) - linux-musl
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Examples - linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: whywaita/actions-cache-s3@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/
|
|
Examples - linux-musl
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Examples - linux-musl
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Cranelift - no-std - windows-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1, whywaita/actions-cache-s3@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/
|
|
Cranelift - no-std - windows-x64
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Cranelift - no-std - windows-x64
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|