-
Notifications
You must be signed in to change notification settings - Fork 214
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: Luohuayu/CatServer
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.12.2
Could not load branches
Nothing to show
Loading
...
head repository: barkeser2002/CatServer
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.12.2
Could not load branches
Nothing to show
Loading
- 2 commits
- 7 files changed
- 1 contributor
Commits on Jun 6, 2026
-
Update Forge to 1.12.2-14.23.5.2864
Bump bundled Forge from build 2860 to 2864 (latest 1.12.2 release, 2025年12月03日). The only server-side source change across builds 2861-2864 is the BiomeDictionary infinite-recursion fix (upstream MinecraftForge #10725, commit 25c661a7f); the remaining upstream commits are CI/MDK build-infra only and do not apply to CatServer. - BiomeDictionary.ensureHasTypes: avoid recursing through getTypes() in the warn message, read BiomeInfo.types directly - ForgeVersion.buildVersion: 2860 -> 2864 - README badges: Forge 14.23.5.2860 -> 14.23.5.2864
barkeser2002 committedJun 6, 2026 -
Add GitHub Actions workflow to build the 1.12.2 universal jar
Builds on JDK 8 (required by Gradle 4.9 / ForgeGradle 2.3): runs `gradlew setup` then `gradlew build` and uploads the resulting jar as an artifact. Pre-creates build/distributions and build/libs so the cleanBuildDir() call in build.gradle does not NPE on a fresh checkout.
barkeser2002 committedJun 6, 2026
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1.12.2...1.12.2