feat(deps)!: bump minestom to 2026.07.12-26.2 - #3
Merged
Conversation
Move the managed net.minestom:minestom constraint from 2026.06.20-26.1.2 (MC 26.1.2) to 2026.07.12-26.2 (MC 26.2, protocol 776) so every BOM consumer lands on the same Minecraft version as the clients and the proxy. Minestom 26.2 reports 148 binary-incompatible changes against 26.1.2, so this is a breaking bump for consumers: registry keys, packet layout, entity metadata and data components all moved. The Grounds libraries on the lobby classpath (grounds-minestom-runtime, plugin-agones-minestom, plugin-permissions-minestom) only touch MinecraftServer, EventNode, Task and the player events, none of which changed, and they resolve and boot cleanly against 26.2. Verified: ./gradlew build green (stable-constraint check + consumer fixture); published as 0.2.0 to mavenLocal and the lobby builds, boots and answers a server-list ping as MC 26.2 / protocol 776 against it.
This was referenced Jul 12, 2026
hbrombeer
marked this pull request as ready for review
July 12, 2026 19:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The lobby (and the rest of the Minestom fleet) needs to move to Minecraft 26.2. The Minestom version is managed centrally here, so this is the first link in the chain.
What
net.minestom:minestomconstraint:2026.06.20-26.1.2→2026.07.12-26.2(upstream release).Breaking
Minestom reports 148 binary-incompatible changes vs 26.1.2 (registry keys, packet layout, entity metadata, data components). Marked
feat!so release-please cuts a minor/major rather than a patch.The Grounds libraries that sit on the lobby classpath —
grounds-minestom-runtime,plugin-agones-minestom,plugin-permissions-minestom— only useMinecraftServer,EventNode,Task/TaskScheduleand the player events. None of those are on the break list, and all three resolve and boot cleanly against 26.2 without recompilation.Verification
./gradlew buildgreen — includes the stable-version constraint check (2026.07.12-26.2is a stable string) and the consumer fixture.0.2.0to mavenLocal;minestom-lobbybuilds against it, boots, and answers a server-list ping as MC 26.2 / protocol 776.Release chain
Merge and release this first — groundsgg/minestom-lobby then consumes
grounds-dependencies:0.2.0. That lobby PR's CI stays red until0.2.0is published.Note: this BOM also pins
io.papermc.paper:paper-apiat26.1.2andcom.velocitypowered:velocity-apiat3.4.0. Both are deliberately left alone here — see the summary on the Paper backends still being on 26.1.2.