Skip to content

feat(forge): update SpongeForge for Forge 62.0.2 / MC 26.1 #2579

feat(forge): update SpongeForge for Forge 62.0.2 / MC 26.1

feat(forge): update SpongeForge for Forge 62.0.2 / MC 26.1 #2579

Triggered via push March 28, 2026 01:36
Status Failure
Total duration 8m 43s
Artifacts 2

deploy.yaml

on: push
Matrix: build / build
Matrix: integrationTest / integrationTest
Waiting for pending jobs
Matrix: publish
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
build / build (vanilla)
Process completed with exit code 1.
build / build (forge)
Process completed with exit code 1.
build / build (vanilla)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf. 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 / build (neoforge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3. 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 / build (forge)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@d4323d4df104b026a6aa633fdb11d772146be0bf. 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
Sponge neoforge Jars
23.6 MB
sha256:3a69884be126fc27fc8c266e451e963d434c929cd29233b1d106da18ebf1c223
SpongeNeo Production Jar
6.86 MB
sha256:c9f63a612548d54f112f3427bf5dc5f2a1f7c14a23d7c1a7bdff6e398b01b007