[darbyjack]

Summary

Fixes the failing Build run on main by dropping a repository that is no longer needed, and moves the workflow onto current stable action majors.

Root cause of the CI failure

https://maven.devs.beer/ was returning HTTP 522 for every request. Gradle walks the repository list in declaration order, and devs.beer sat ahead of jitpack.io. That meant Gradle sent the three JitPack dependencies to devs.beer first and treated the 522 as a hard failure, so the build died before it ever tried JitPack:

Execution failed for task ':compileJava'
> Could not resolve all files for configuration ':compileClasspath'
   > Could not resolve com.github.milkbowl:VaultAPI:1.7.1.
      > Could not GET 'https://maven.devs.beer/com/github/milkbowl/VaultAPI/1.7.1/VaultAPI-1.7.1.pom'.
        Received status code 522 from server: <none>

beer.devs:itemsadder-api was the only dependency that needed devs.beer. It is published to Maven Central, which is already declared, so the repository has no remaining job.

The diff

 repositories {
     mavenCentral()
     maven("https://repo.papermc.io/repository/maven-public/")
     maven("https://repo.extendedclip.com/content/repositories/placeholderapi/")
     maven("https://nexus.phoenixdevt.fr/repository/maven-public/")
     maven("https://repo.momirealms.net/releases/")
     maven("https://repo.nexomc.com/releases/")
     maven("https://repo.oraxen.com/releases")
-    maven("https://maven.devs.beer/")
     maven("https://jitpack.io")
 }

Action version bumps

Action	Before	After
actions/checkout	v4	v7
actions/setup-java	v4	v6
gradle/actions/setup-gradle	v3	v6
actions/upload-artifact	v4.3.3	v7

Each hop between these majors is a Node 24 or ESM migration. No input names, defaults, or step behaviour changed in a way this workflow depends on, so the steps keep working as written:

• checkout v5 through v7: Node 24, then creds to a separate file, then ESM. v7 only blocks fork checkouts on pull_request_target and workflow_run, neither of which this workflow uses.
• setup-java v5 and v6: Node 24, then an ESM packaging change. java-version and distribution are unchanged inputs.
• gradle/actions v4 removes the deprecated arguments parameter (unused here), v5 is Node 24, v6 drops partial config-cache support (this workflow does not enable the config cache).
• upload-artifact v5 through v7: Node 24, then ESM, then a new opt-in archive: false input for direct file uploads. The default name, path, and zip behaviour are unchanged.

All four require runner v2.327.1 or newer. GitHub-hosted ubuntu-latest runners already satisfy that.

Evidence

Before, from run 36501562468 on main:

Could not resolve com.github.Ssomar-Developement:SCore:5.25.3.9.
   Could not GET 'https://maven.devs.beer/com/github/Ssomar-Developement/SCore/5.25.3.9/SCore-5.25.3.9.pom'.
     Received status code 522 from server: <none>
BUILD FAILED in 1m 47s

After, verified locally against an empty GRADLE_USER_HOME, so every artifact was downloaded fresh with the repository list as committed:

> Task :compileJava
BUILD SUCCESSFUL in 10s

beer.devs:itemsadder-api:4.0.18-beta-10 resolves from Central, and the full build task plus shadowJar (what the workflow runs) succeeds:

> Task :build
BUILD SUCCESSFUL in 8s
-rw-r--r-- 2909995 build/libs/DeluxeMenus-1.14.2-DEV-pr-e5e1834a.jar

Merge Danger

Door: two-way. Reverting the commit restores the previous repository list and action versions.

Blast Radius: build-only. No plugin source, dependency coordinates, or versions change, so the shaded jar is byte-for-byte the same set of inputs as before.