Skip to content

chore: bump NeoForge 26.2.0.43-beta -> 26.2.0.49-beta, fabric-loom 1.17.17 -> 1.17.18 - #116

Open
TheMarstonConnell wants to merge 1 commit into
26.xfrom
chore/bump-26.2.0.49-beta
Open

chore: bump NeoForge 26.2.0.43-beta -> 26.2.0.49-beta, fabric-loom 1.17.17 -> 1.17.18#116
TheMarstonConnell wants to merge 1 commit into
26.xfrom
chore/bump-26.2.0.49-beta

Conversation

@TheMarstonConnell

Copy link
Copy Markdown
Owner

Summary

Same Minecraft line (26.2). A newer NeoForge beta build and a fabric-loom patch release are available; every other tracked dependency is already current for MC 26.2, so this is a build-tooling-only bump with no code migration.

Version changes

Field Old New
neo_version / neo_version_range 26.2.0.43-beta 26.2.0.49-beta
net.fabricmc.fabric-loom (build.gradle) 1.17.17 1.17.18

Unchanged (already current for MC 26.2): minecraft_version 26.2, neo_form_version 26.2-2, fabric_version 0.156.0+26.2, fabric_loader_version 0.19.3, forge_config_api_port_version 26.2.1, net.neoforged.moddev 2.0.143.

Files changed

  • gradle.propertiesneo_version, neo_version_range
  • build.gradlenet.fabricmc.fabric-loom plugin version

No doc sync needed (Minecraft line unchanged). No migration fixes required — no MC-line crossing, so no vanilla/NeoForge/Fabric API renames to chase.

Verification (local)

All three commands ran locally against a checksum-pinned Gradle 9.5.0 distribution:

  • ./gradlew --refresh-dependencies buildBUILD SUCCESSFUL (both NeoForge + Fabric jars, plus NeoForge unit tests)
  • ./gradlew :neoforge:runGameTestServerBUILD SUCCESSFUL, All 41 required tests passed :)
  • ./gradlew :fabric:runGametestBUILD SUCCESSFUL, All 39 required tests passed :)

Both loaders build and both gametest suites are green.

🤖 Generated with Claude Code


Generated by Claude Code

…17.17 -> 1.17.18

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants