Skip to content
.github/workflows/build.yml

chore(deps): bump actions/checkout from 4 to 6 #1303

Sign in to view logs

chore(deps): bump actions/checkout from 4 to 6

chore(deps): bump actions/checkout from 4 to 6 #1303

Triggered via push March 30, 2026 15:52
@ShrBoxShrBox
pushed f9c9d3a
develop
Status Success
Total duration 40m 19s
Artifacts 8

build.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build (quickjs, server)
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. 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/
build (lua, server)
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. 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/
build (python, server)
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. 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/
build (nodejs, server)
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. 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/
build (python, client)
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. 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/
build (lua, client)
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. 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/
build (nodejs, client)
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. 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/
build (quickjs, client)
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. 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
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-client-lua-windows-x64 Expired
20.3 MB
sha256:0691276fc3c1b3b2102a7210408d371cdde9ae4e6033cb454e170ab5e4938169
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-client-nodejs-windows-x64 Expired
20.8 MB
sha256:5349b73a85880b396f7609ba933800eb5b82b467da14b5752e672d7ddc21642c
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-client-python-windows-x64 Expired
20.7 MB
sha256:ab8167452ba96096677987fffd7cfd7b03f1168669a6345bd99d1debef53583c
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-client-quickjs-windows-x64 Expired
20.6 MB
sha256:ac1c972e97eae24d3751545b3d78f4c63906b1164454c3db8fb15f7ce40aa8ad
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-server-lua-windows-x64 Expired
20.3 MB
sha256:f6d12abc6f25dea10c1ee8c00377d7bd180c6fe8c254dc1aa52aaf41388d80e6
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-server-nodejs-windows-x64 Expired
20.8 MB
sha256:fc3095ba7962612ea54b3786981ac3ed759f8c739e27f93b849be491124a2029
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-server-python-windows-x64 Expired
20.8 MB
sha256:5cb40977ba0e1d60357ce366159b1e6e2e172b3c73759f997aeff73fb08dc5ab
LegacyScriptEngine-f9c9d3a9171af756fe449c8902b8b089abaccd09-server-quickjs-windows-x64 Expired
20.6 MB
sha256:77257c81b5add7c009a0f2de8b38e5aca043f805f80c2a921636e202f817faf6