Skip to content
.github/workflows/build.yml

chore: update CHANGELOG.md and tooth.json #1311

Sign in to view logs

chore: update CHANGELOG.md and tooth.json

chore: update CHANGELOG.md and tooth.json #1311

Triggered via push March 31, 2026 16:13
@ShrBoxShrBox
pushed 9b6e317
main
Status Success
Total duration 15m 46s
Artifacts 8

build.yml

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

Annotations

8 warnings
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 (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 (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 (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-9b6e31780f856f17d7c8e171793f5f4b94694ddd-client-lua-windows-x64 Expired
20.3 MB
sha256:119a9fe1432a2555da622eb1d973506ceb8cef5fc9d942b2f8ea26b930060c9b
LegacyScriptEngine-9b6e31780f856f17d7c8e171793f5f4b94694ddd-client-nodejs-windows-x64 Expired
20.9 MB
sha256:3af46b0aa23153655e0f4714eb1d80fd95e5132513f42adb116ed33d29311950
LegacyScriptEngine-9b6e31780f856f17d7c8e171793f5f4b94694ddd-client-python-windows-x64 Expired
20.8 MB
sha256:77d37b83a0b0c1614b35582cf6a2b7b7652cfb7bb541cc1978dfeabe37d72c94
LegacyScriptEngine-9b6e31780f856f17d7c8e171793f5f4b94694ddd-client-quickjs-windows-x64 Expired
20.6 MB
sha256:66521ab3da1b3cc39122754b214a9ef6f95d0596539412723356252337339384
LegacyScriptEngine-9b6e31780f856f17d7c8e171793f5f4b94694ddd-server-lua-windows-x64 Expired
20.3 MB
sha256:c26417dc385e1df67874293cb2b254107715a35563daf41cbc1a0c76734c4b1f
LegacyScriptEngine-9b6e31780f856f17d7c8e171793f5f4b94694ddd-server-nodejs-windows-x64 Expired
20.9 MB
sha256:15a3ace96409a4eba163bbf16b634923cfe180e01e6a34ce0905b5ffe8572c00
LegacyScriptEngine-9b6e31780f856f17d7c8e171793f5f4b94694ddd-server-python-windows-x64 Expired
20.8 MB
sha256:b917cece9dfb749cf28671d5f9dce5502017bdaa1db3ff4b411b66ffd912061e
LegacyScriptEngine-9b6e31780f856f17d7c8e171793f5f4b94694ddd-server-quickjs-windows-x64 Expired
20.6 MB
sha256:72621774dedf5deff75321de748573bfbba8cf94a8e2aab5a47f2a61745be16c