Update client #24
Coloryrserver.yml
on: push
build_folia
56s
build_paper
1m 5s
build_velocity
2m 17s
build_fabric_1_16_5
2m 12s
build_fabric_1_20_1
2m 55s
build_fabric_1_21
1m 57s
build_fabric_1_21_6
3m 33s
build_fabric_1_21_11
3m 2s
build_forge_1_7_10
4m 55s
build_forge_1_12_2
4m 53s
build_forge_1_16_5
3m 43s
build_forge_1_20_1
3m 13s
build_neoforge_1_21
7m 46s
build_neoforge_1_21_6
10m 12s
build_neoforge_1_21_11
6m 0s
Annotations
3 errors and 30 warnings
|
build_folia
Process completed with exit code 1.
|
|
build_fabric_1_21
Process completed with exit code 1.
|
|
build_fabric_1_21_6
Process completed with exit code 1.
|
|
build_folia
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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_folia
Failed to restore gradle-home-v1|Windows|build_folia[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_paper
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_paper
Failed to restore gradle-home-v1|Windows|build_paper[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_fabric_1_21
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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_fabric_1_21
Failed to restore gradle-home-v1|Windows|build_fabric_1_21[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_fabric_1_16_5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_fabric_1_16_5
Failed to restore gradle-home-v1|Windows|build_fabric_1_16_5[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_velocity
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_velocity
Failed to restore gradle-home-v1|Windows|build_velocity[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_fabric_1_20_1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_fabric_1_20_1
Failed to restore gradle-home-v1|Windows|build_fabric_1_20_1[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_fabric_1_21_11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_fabric_1_21_11
Failed to restore gradle-home-v1|Windows|build_fabric_1_21_11[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_forge_1_20_1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_forge_1_20_1
Failed to restore gradle-home-v1|Windows|build_forge_1_20_1[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_fabric_1_21_6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v3. 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_fabric_1_21_6
Failed to restore gradle-home-v1|Windows|build_fabric_1_21_6[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_forge_1_16_5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_forge_1_16_5
Failed to restore gradle-home-v1|Windows|build_forge_1_16_5[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_forge_1_12_2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_forge_1_12_2
Failed to restore gradle-home-v1|Windows|build_forge_1_12_2[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_forge_1_7_10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_forge_1_7_10
Failed to restore gradle-home-v1|Windows|build_forge_1_7_10[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_neoforge_1_21_11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_neoforge_1_21_11
Failed to restore gradle-home-v1|Windows|build_neoforge_1_21_11[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_neoforge_1_21
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_neoforge_1_21
Failed to restore gradle-home-v1|Windows|build_neoforge_1_21[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
|
build_neoforge_1_21_6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v3. 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_neoforge_1_21_6
Failed to restore gradle-home-v1|Windows|build_neoforge_1_21_6[f568350f77af9e166c39c785cbe47458]-faa7aff4d97b9d8325d2c9ab776d7217542a8bba: Error: Cache service responded with 400
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
allmusic_server_fabric_1_16_5
Expired
|
16.8 MB |
sha256:87c7539a94246d610bdc27b5b4d0f5a19cbbcc104225d6001c6b62dc4bbf2d04
|
|
|
allmusic_server_fabric_1_20_1
Expired
|
17.3 MB |
sha256:85e8f39e7d6195c634bbb4b4035bbf9e43c81607fdeda3fcf81f929b20028c64
|
|
|
allmusic_server_fabric_1_21_11
Expired
|
17.5 MB |
sha256:247df5ddd0ba3ed5f9124db71978ca64330e9ad9598fb914a364d29b0921e88e
|
|
|
allmusic_server_forge_1_12_2
Expired
|
33.5 MB |
sha256:bc59b4c989b6bc61952a928b294b616bdeccafec3712dc9fa58d76228f087a4a
|
|
|
allmusic_server_forge_1_16_5
Expired
|
16.5 MB |
sha256:0b523f7ba4bd7b1d486f942d361e1d63787c6c3f63dd1841f72f5408484e6f22
|
|
|
allmusic_server_forge_1_20_1
Expired
|
18.2 MB |
sha256:bce88f405cbbf31fde048413e317d386112a7660b4d45656a54efa056c62baf6
|
|
|
allmusic_server_forge_1_7_10
Expired
|
33.5 MB |
sha256:2f7bc3cc51efe7e46e6a4f90f42116b653134e14d3cd2a8787c4550308658f52
|
|
|
allmusic_server_neoforge_1_21
Expired
|
16.9 MB |
sha256:114b327ed4f9d1930c9c914a470e07f5cf4133644f267d6fa47d79e1ea6a972f
|
|
|
allmusic_server_neoforge_1_21_11
Expired
|
16.7 MB |
sha256:5eefe6f318f4498cd8565e601e613e94050e2a98ccb699cd0a161b9befd0067d
|
|
|
allmusic_server_neoforge_1_21_6
Expired
|
16.9 MB |
sha256:bd5096bfd097b212d373235a182bb9045bfb4a9ac4c0d08f85e2f00193720c5e
|
|
|
allmusic_server_paper
Expired
|
2.47 MB |
sha256:db4fa67cb26f04bdbcb06013e5e80a0028bad60711b2c1519a01d09e5331667b
|
|
|
allmusic_server_velocity
Expired
|
15.9 MB |
sha256:5e1b7079cf89f92c59bb394feb3888d901b67c30e8ea3641dc2b1a9034d50d7f
|
|