Skip to content

Prepare for new release (#421) #287

Prepare for new release (#421)

Prepare for new release (#421) #287

Triggered via push March 20, 2026 20:40
Status Success
Total duration 29m 28s
Artifacts 8
benchmarks  /  ...  /  build-wasm-examples
12m 19s
benchmarks / build-wasm-examples / build-wasm-examples
Matrix: benchmarks / benchmark
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Workflow syntax warning: .github/workflows/CreateRelease.yml#L20
.github/workflows/CreateRelease.yml (Line: 20, Col: 9): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
benchmarks / build-wasm-examples / build-wasm-examples
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, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
benchmarks / benchmark (kvm, amd, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
benchmarks / benchmark (kvm, intel, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
benchmarks / benchmark (mshv3, intel, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
benchmarks / benchmark (mshv3, amd, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
benchmarks / benchmark (hyperv, amd, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
benchmarks / benchmark (hyperv, intel, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, actions/upload-artifact@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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/
publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. 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
benchmarks_Linux_kvm_amd
432 KB
sha256:6e45243491e31e16549f3d737a73c2e99a5b713c50b66d46008a2c7eeb1c4806
benchmarks_Linux_kvm_intel
435 KB
sha256:bc3574e85628810125c16cf1b7bedd1e1a9e112818ae857287a275989554e090
benchmarks_Linux_mshv3_amd
430 KB
sha256:7a3a54d616992b67ddd586a3ac95e15e1657a4c99235c1418e3d2478d1920726
benchmarks_Linux_mshv3_intel
427 KB
sha256:77dca1ec1b28357654bf1dd4db82deaf2fc74fc99099d879ffe1c44145b21e59
benchmarks_Windows_hyperv_amd
181 KB
sha256:d56bdfb073ba96418d43c3a31856df985824a120c3f6df65dd1b77456960cd8b
benchmarks_Windows_hyperv_intel
180 KB
sha256:c2bfa859111aca363ecf58987c80f1049398ad28a164fc44a29f3727d46d96ae
guest-modules
128 KB
sha256:c4daef03de92d541ba12ec6d988c4c515ddf7f52c8d946800a1113c88c30e5a3
hyperlight-dev~hyperlight-wasm~RHYMSK.dockerbuild
36.4 KB
sha256:09faf4ffff89bf63079b6d2f8dd6221df59a1fb9405db356bb5af153f91e7c0d