Skip to content

re-added Curios support (NeoForge) #217

re-added Curios support (NeoForge)

re-added Curios support (NeoForge) #217

Triggered via push March 28, 2026 11:22
Status Success
Total duration 6m 57s
Artifacts 1
Publish Github  /  Publish Github
9s
Publish Github / Publish Github
Publish Forge on Curseforge  /  Publish Curseforge
8s
Publish Forge on Curseforge / Publish Curseforge
Publish Forge on Modrinth  /  Publish Modrinth
12s
Publish Forge on Modrinth / Publish Modrinth
Publish Neoforge on Curseforge  /  Publish Curseforge
6s
Publish Neoforge on Curseforge / Publish Curseforge
Publish Neoforge on Modrinth  /  Publish Modrinth
11s
Publish Neoforge on Modrinth / Publish Modrinth
Publish Fabric on Curseforge  /  Publish Curseforge
8s
Publish Fabric on Curseforge / Publish Curseforge
Publish Fabric on Modrinth  /  Publish Modrinth
8s
Publish Fabric on Modrinth / Publish Modrinth
Fit to window
Zoom out
Zoom in

Annotations

7 warnings and 1 notice
Publish Github / Publish Github
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: softprops/action-gh-release@v2. 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/
Publish Neoforge on Curseforge / Publish Curseforge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Kir-Antipov/mc-publish@v3.3.0. 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/
Publish Forge on Curseforge / Publish Curseforge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Kir-Antipov/mc-publish@v3.3.0. 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/
Publish Fabric on Modrinth / Publish Modrinth
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Kir-Antipov/mc-publish@v3.3.0. 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/
Publish Fabric on Curseforge / Publish Curseforge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Kir-Antipov/mc-publish@v3.3.0. 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/
Publish Neoforge on Modrinth / Publish Modrinth
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Kir-Antipov/mc-publish@v3.3.0. 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/
Publish Forge on Modrinth / Publish Modrinth
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Kir-Antipov/mc-publish@v3.3.0. 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
Submitted dependency-graph-reports/cicd-build.json: The snapshot was accepted, but it is not for the default branch. It will not update dependency results for the repository.

Artifacts

Produced during runtime
Name Size Digest
gradle-build
596 KB
sha256:7a65027ccac56f524b217ddf05c57dce27b77569591f7a34a571c6e8eecc7153