7.4.3 raises Java floor from 21 to 25 in a patch release

[svaningelgem]

WorldEdit 7.4.3 raises the minimum Java version from 21 to 25, but
ships as a patch bump over 7.4.2 with no callout in the release notes.

Class file evidence:

$ unzip -p worldedit-core-7.4.2.jar com/sk89q/worldedit/EditSession.class         | xxd | head -1
00000000: cafe babe 0000 0041 ...   # 0x41 = 65 (Java 21)

$ unzip -p worldedit-core-7.4.3.jar com/sk89q/worldedit/EditSession.class         | xxd | head -1
00000000: cafe babe 0000 0045 ...   # 0x45 = 69 (Java 25)

This isn't just a toolchain pin — the source itself now depends on Java 25 APIs:

• ScopedValue (used in Request.java:34) — preview in 21–24, stable only in 25. Cannot be compiled on 21–24 without preview flags.
• Unnamed variables (var _) — preview pre-22, stable in 22+. Won't compile on 21.

So 7.4.3 genuinely cannot be built or consumed by anything below JDK 25.

Impact on downstream plugins: anyone compiling against the WorldEdit API with a JDK < 25 now breaks with:

bad class file: .../worldedit-core-7.4.3.jar(.../EditSession.class)
  class file has wrong version 69.0, should be 66.0

The bump appears to have come in via #2959 ("Move 21 into only old adapters, set launcher for paperweight").

A Java-floor jump of four major versions is a meaningful compatibility break — would you consider:

1. Re-cutting this as 7.5.0 (or yanking 7.4.3 and re-releasing), and
2. Calling out the Java 25 floor prominently in the release notes going forward?

Thanks!

[octylFractal]

This is essentially required by targeting Minecraft - we cannot assemble most integrations without using 25, so we keep it consistent across the entire library. We generally don't call it out because we don't treat new MC versions as breaking either, but we do expect that you'll be building against them and would need to raise your Java version regardless.

I would treat any MC version bump in the patch notes as potentially causing a Java version bump too.

[svaningelgem]

Thanks for the feedback! I'm indeed raising my version, but still targeting my old JDK (as nothing in my source tree warrants 25 yet)

[me4502]

For some extra context, when we didn't immediately bump the Java version last time MC did, it caused some major downstream issues due to MC-related gradle tooling. It's the kind of situation where it's not ideal either way, but matching what MC does ends up being cleaner overall.

Including it in changelogs makes sense, but the bump itself isn't really avoidable.