Merge pull request 'CI: setup-java v5 and Gradle build cache' (#20) from ci-caching into master

Reviewed-on: #20

.gitea/workflows/check.yml

@@ -1,12 +1,11 @@
 name: Check
 
-# Compiles every Minecraft version on pull requests and on pushes to master,
+# Compiles every Minecraft version on pull requests, so a change that breaks
-# so a change that breaks one version (e.g. a missed or bad port) fails before
+# one version (e.g. a missed or bad port) fails before it's merged instead of
-# it's merged instead of in the release build.
+# in the release build. Merges to master aren't re-checked: the PR already
+# checked that code.
 on:
   pull_request:
-  push:
-    branches: [master]
 
 jobs:
   compile:
@@ -17,8 +16,11 @@ jobs:
         with:
           submodules: true
 
+      # The JDK comes from the runner's tool cache. `cache: gradle` stores Gradle's
+      # dependencies, Loom's Minecraft cache and the build cache in the runner's
+      # actions cache.
       - name: Set up Java 21
-        uses: actions/setup-java@v4
+        uses: actions/setup-java@v5
         with:
           distribution: temurin
           java-version: 21

.gitea/workflows/release.yml

@@ -44,8 +44,11 @@ jobs:
           fi
           echo "Building Saturn Client $MOD_VERSION"
 
+      # The JDK comes from the runner's tool cache. `cache: gradle` stores Gradle's
+      # dependencies, Loom's Minecraft cache and the build cache in the runner's
+      # actions cache.
       - name: Set up Java 21
-        uses: actions/setup-java@v4
+        uses: actions/setup-java@v5
         with:
           distribution: temurin
           java-version: 21

gradle.properties

@@ -1,5 +1,7 @@
 org.gradle.jvmargs=-Xmx3G
 org.gradle.parallel=true
+# Reuse task outputs (e.g. compiled classes) when inputs haven't changed.
+org.gradle.caching=true
 
 # IntelliJ IDEA is not yet fully compatible with configuration cache, see: https://github.com/FabricMC/fabric-loom/issues/1349
 org.gradle.configuration-cache=false