ChestShop build broken by upstream: WorldGuard 7.1.0-SNAPSHOT moved to a Java 25 toolchain

ChestShop · Build and ChestShop · Test & Coverage fail on develop at :chestshop:compileJava:

> Could not resolve com.sk89q.worldguard:worldguard-core:7.1.0-SNAPSHOT.
  > Dependency resolution is looking for a library compatible with JVM runtime version 21,
    but '...:7.1.0-SNAPSHOT:20260801.040158-16' is only compatible with JVM runtime version 25 or newer.

Cause

No commit of ours is involved — chestshop/build.gradle.kts tracked the moving com.sk89q.worldguard:*:7.1.0-SNAPSHOT, and EngineHub moved their toolchain to Java 25. The snapshot published 2026-08-01 (20260801.040158-16) declares org.gradle.jvm.version: 25, which Gradle refuses against our Java 21 toolchain. Nothing had rebuilt on develop since 2026-07-20, so it surfaced on the next push.

This is the same failure mode already handled for WorldEdit (force-pinned to 7.3.9 when 8.0.0-SNAPSHOT went Java 25) — WorldGuard has now followed.

Fix

Pin WorldGuard to 7.0.17, the last release built for Java 21 (verified from Gradle module metadata: 7.0.12–7.0.17 → jvm 21; 7.0.18 and 7.1.0-SNAPSHOT → jvm 25). Declared as compileOnly non-transitive as before, plus a force(...) alongside the existing WorldEdit pins so no path can reintroduce the moving snapshot.

Verified

• :chestshop:compileJava — BUILD SUCCESSFUL (all touched classes still resolve: WorldGuard, WorldGuardPlugin, WorldGuardPlatform, BukkitWorldConfiguration, RegionPermissionModel, ApplicableRegionSet, Flags, StateFlag, FlagConflictException, RegionManager, LocalPlayer).
• :chestshop:test — BUILD SUCCESSFUL.

Note

The soft-depend APIs are now pinned to a Java 21 ceiling. Whenever the monorepo toolchain moves past 21, these pins can and should be lifted to current WorldGuard/WorldEdit.