Skip to content

Add the NeoForgedRepositoryFilter to address the issues associated with NeoForge Maven using the Maven Central repository #746

Add the NeoForgedRepositoryFilter to address the issues associated with NeoForge Maven using the Maven Central repository

Add the NeoForgedRepositoryFilter to address the issues associated with NeoForge Maven using the Maven Central repository #746

Triggered via pull request March 19, 2026 18:17
@Gu-ZTGu-ZT
synchronize #328
Gu-ZT:fix/327
Status Failure
Total duration 2m 4s
Artifacts 1

build-prs.yml

on: pull_request
Matrix: test-project
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 13 warnings
Test testproject on ubuntu-latest (no recomp)
Process completed with exit code 1.
Test testproject on ubuntu-latest (recomp)
The strategy configuration was canceled because "test-project.ubuntu-latest_testproje_2" failed
Test testproject on ubuntu-latest (recomp)
Process completed with exit code 1.
Test testproject on windows-latest (recomp)
The strategy configuration was canceled because "test-project.ubuntu-latest_testproje_2" failed
Test testproject on windows-latest (recomp)
The operation was canceled.
Build / build
Process completed with exit code 1.
Test testproject on windows-latest (no recomp)
The strategy configuration was canceled because "test-project.ubuntu-latest_testproje_2" failed
Test testproject on windows-latest (no recomp)
The operation was canceled.
Test legacytest on ubuntu-latest (no recomp)
The strategy configuration was canceled because "test-project.ubuntu-latest_testproje_2" failed
Test legacytest on ubuntu-latest (no recomp)
The operation was canceled.
Test legacytest on ubuntu-latest (recomp)
The strategy configuration was canceled because "test-project.ubuntu-latest_testproje_2" failed
Test legacytest on ubuntu-latest (recomp)
The operation was canceled.
Test testproject on ubuntu-latest (no recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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. 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/
Test testproject on ubuntu-latest (no recomp)
Failed to restore gradle-home-v1|Linux|test-project[e29df6d0aa509f25b2d5bf2d3d960b21]-664205393da7207fcf44a6c6884efe0f7e85c030: Error: Cache service responded with 400
Test testproject on ubuntu-latest (recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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. 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/
Test testproject on ubuntu-latest (recomp)
Failed to restore gradle-home-v1|Linux|test-project[2ad46fe45b69ee45d2c95e9fb1a04a4b]-664205393da7207fcf44a6c6884efe0f7e85c030: Error: Cache service responded with 400
Test testproject on windows-latest (recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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. 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/
Test testproject on windows-latest (recomp)
Failed to restore gradle-home-v1|Windows|test-project[3567a86f426703062338d8edf356d2e2]-664205393da7207fcf44a6c6884efe0f7e85c030: Error: Cache service responded with 400
Build / build
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/upload-artifact@v4, gradle/actions/setup-gradle@v4. 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/
Test testproject on windows-latest (no recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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. 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/
Test testproject on windows-latest (no recomp)
Failed to restore gradle-home-v1|Windows|test-project[2748f45af103653aaa2766d65b60993f]-664205393da7207fcf44a6c6884efe0f7e85c030: Error: Cache service responded with 400
Test legacytest on ubuntu-latest (no recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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. 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/
Test legacytest on ubuntu-latest (no recomp)
Failed to restore gradle-home-v1|Linux|test-project[4f83567ab5d9ed5f2d42cd754d2ce41f]-664205393da7207fcf44a6c6884efe0f7e85c030: Error: Cache service responded with 400
Test legacytest on ubuntu-latest (recomp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@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. 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/
Test legacytest on ubuntu-latest (recomp)
Failed to restore gradle-home-v1|Linux|test-project[40e433df232248ad1667e88840caf8c1]-664205393da7207fcf44a6c6884efe0f7e85c030: Error: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
reports
79.3 KB
sha256:200ddb094408675ac5a61361a2865c27a7f6aceb73a8903924b4d0612db399d3