[dependabot]

Bumps net.minestom:testing from 2026.09.12-26.2 to 2026.10.07-26.2.

Release notes

Sourced from net.minestom:testing's releases.

2026.10.07-26.2

It is recommended to update to receive the latest security fixes. An advisory will be disclosed at a later date.

What's Changed

• docs: describe migration notes for breaking changes by @​kermandev in Minestom/Minestom#3403

Full Changelog: Minestom/Minestom@2026.10.05-26.2...2026.10.07-26.2

2026.10.05-26.2

This is a breaking release. APIs that were deprecated for removal are gone, ServerFlag is replaced by the new ServerProperties API, and registry keys are created with RegistryKey.of and TagKey.of. Several packets were fixed to match the protocol, which changes some packet constructors and accessors. Every breaking change has a before and after example in the migration section at the bottom.

This release also continues the registry work from 26.2. Instances, packet buffers, and component serializers can use registries other than those of the running server process, which makes Minestom easier to use in tests and without a server process at all.

This is not the last breaking release of this cycle before 26.3, it is just a checkpoint for some of the work already completed.

26.3

26.3 is still being worked on. If you require 26.3 early, you can use the published snapshot located within Minestom/Minestom#3369.

Registries

Registries are a core part of this changeset so far, they will continue to be larger changeset until registry v3 is merged.

RegistryKey.of and TagKey.of are now the public way to create keys, replacing the internal unsafeOf methods (#3401). A key is only a typed name. Its syntax is validated, but registry membership is not, so the same key can name an entry in one registry and nothing in another. Looking up a key that has no entry returns null, or -1 for IDs.

RegistryKey<Biome> moon = RegistryKey.of("minestom:moon");
TagKey<Block> soft = TagKey.of("minestom:soft");

Instances can be created with the registry context of your choice (#3402). InstanceManager#createInstanceContainer has overloads that take Registries, and the Instance and InstanceContainer constructors without a registry context are deprecated.

InstanceContainer instance = instanceManager.createInstanceContainer(registries, DimensionType.OVERWORLD);

A number of places read the registries of the global server process instead of the registries they were given:

• Copied and shared instances keep the registries and dimension name of their source instance (#3392).
• Players read dimension type IDs from the current server process instead of the first one (#3394).
• EnchantmentTableInventory looks up enchantment IDs in the registry it was created with (#3391).
• Item components in hover events are encoded with the buffer registries (#3400), and maxLength checks measure typed NBT with them as well (#3385).
• Raw values decoded with different registry contexts compare equal (#3390).
• NbtComponentSerializer.nbt(Registries) serializes components without an initialized server process (#3388).

Buffers from PacketVanilla.PACKET_POOL hold no registries until a write sets them (#3396). Code that takes a buffer from the pool directly must set its registries before writing registry dependent types.

New and reset chunk sections fill their biome palette with the ID of Biome.PLAINS in the instance registries, instead of ID 0 (#3370). Section#clear() is removed. Future release will change the ordering where id 0 is no longer Biome.PLAINS.

... (truncated)

Commits

• 97fc987 Merge commit from fork
• fcd35c0 docs: describe migration notes for breaking changes (#3403)
• 46410aa feat: choose the registry context when creating instances (#3402)
• 814d4b0 refactor: create registry keys with of (#3401)
• e26714d chore: bump the non-breaking group with 3 updates (#3397)
• 268866b fix: encode hover item components with the buffer registries (#3400)
• 29988a8 fix: set the registries of pooled packet buffers per write (#3396)
• f6486c0 refactor: use a damage type key and nullable source IDs in DamageEventPacket ...
• 5e7446d fix: read player dimension type IDs from the current process (#3394)
• 4e9811c refactor: remove API deprecated for removal (#3393)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[mergify]

👋 dependabot[bot] your PR is conflicting and needs to be updated to be merged

[dependabot]

Looks like net.minestom:testing is up-to-date now, so this is no longer needed.