Skip to content

[WasmFS] Make the Node backend multi-env compatible (#26624) #11166

[WasmFS] Make the Node backend multi-env compatible (#26624)

[WasmFS] Make the Node backend multi-env compatible (#26624) #11166

Triggered via push April 6, 2026 16:24
Status Success
Total duration 21s
Artifacts 1

ci.yml

on: push
Archive
18s
Archive
Codesize Checks
0s
Codesize Checks
clang-format-diff
0s
clang-format-diff
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Archive
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1. 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/

Artifacts

Produced during runtime
Name Size Digest
emscripten-5.0.6-git
17.8 MB
sha256:564b92503bdfb59f291b38f4f147fa9d9d98e087ba1b7c85711e45ee434251aa