Skip to content

Update dependency com.github.glitchfiend:TerraBlender-neoforge to v26 #1451

Update dependency com.github.glitchfiend:TerraBlender-neoforge to v26

Update dependency com.github.glitchfiend:TerraBlender-neoforge to v26 #1451

Triggered via pull request March 25, 2026 21:20
Status Failure
Total duration 11m 51s
Artifacts 8

gametests.yml

on: pull_request
Matrix: Build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 12 warnings
Build (server, cyclops-all-deps, 1.21.1, neoforge)
Process completed with exit code 255.
Build (client, cyclops-all-deps, 1.21.1, neoforge)
The action has timed out.
Build (server, cyclops-all, 1.21.11, fabric)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (server, cyclops-id, 1.21.11, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (server, cyclops-all, 1.21.1, fabric)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (server, cyclops-all, 1.21.11, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (server, cyclops-all, 1.21.1, forge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (client, cyclops-id, 1.21.1, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (server, cyclops-all-deps, 1.21.1, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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 (server, cyclops-all, 1.21.11, forge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (server, cyclops-all, 1.21.1, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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 (server, cyclops-id, 1.21.1, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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/
Build (client, cyclops-all, 1.21.1, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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 (client, cyclops-all-deps, 1.21.1, neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, robinraju/release-downloader@a96f54c1b5f5e09e47d9504526e96febd949d4c2. 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
cyclops-all-1.21.1-fabric-mods
1.12 MB
sha256:711d44876eaf5e21c6da172918879e973c79dcbee4a9c4a4801f6ab60aec692f
cyclops-all-1.21.1-forge-mods
1.08 MB
sha256:84ba7ec0174cdbbe50289db6cf27ca580c21d6f685a3734e64cec29c2d92e3ad
cyclops-all-1.21.1-neoforge-mods
54.7 MB
sha256:0e6af5f771ec30703333c38bfbff39f0ff4569f140cf482cb2a07b3a11a0363a
cyclops-all-1.21.11-fabric-mods
1.16 MB
sha256:16bd9d4e7f21f12c8b9bca7a9b05878132efd9593b16d9dd779382fe3faa8d2b
cyclops-all-1.21.11-forge-mods
1.12 MB
sha256:479f01dfe3481efb06e887b21f58c2b219d728d555d4452798609ff4e9710957
cyclops-all-1.21.11-neoforge-mods
42.5 MB
sha256:67c2d6a7923b1f01e6c2b068ce8cfa665cf5ecba0429d4ff153e010b73cbaf1e
cyclops-id-1.21.1-neoforge-mods
51.7 MB
sha256:27ffd27f8175975ea0f8f07710f7241697d8130687299818c334b83b3d7e2635
cyclops-id-1.21.11-neoforge-mods
41.9 MB
sha256:2d1425561c29a3a95b774ebb06daeddae78a4593a03250e40930675ca785912d