Skip to content

Support 26.1.2#222

Merged
Zoriot merged 4 commits into
mainfrom
updates
Jun 8, 2026
Merged

Support 26.1.2#222
Zoriot merged 4 commits into
mainfrom
updates

Conversation

@Zoriot

@Zoriot Zoriot commented May 24, 2026

Copy link
Copy Markdown
Member

build(gradle): update dependencies to flexible versions and upgrade Gradle to 9.5.1

Main dependency which needed an update was XSeries in the alpslib, that errored out otherwise.

We don't want to update to Java 25 / Minecraft 26.1.2 yet, to ensure we have no breaking changes i made a compatibility build-

@Zoriot Zoriot requested a review from Cinnazeyy May 24, 2026 21:06
@Zoriot Zoriot self-assigned this May 24, 2026
@Zoriot Zoriot added the enhancement New feature or request label May 24, 2026
@Zoriot

Zoriot commented May 24, 2026

Copy link
Copy Markdown
Member Author

@Cinnazeyy what do you think of using version ranges? I have a split options, on one side it's nice to automatically get new fixes etc. At the same time it might also pull things in we don't want. Even through it should be save for libs which uses sem ver. Plugins might be a problem trough.

Biggest downside is that builds are not reproducable anymore with that, so maybe no that good for the plugins itself, but only for the libs.
Or we decide when to use and when not.
I would probably still pin dependencies to specific versions, except paper maybe. For library all can be version ranges imo.
https://docs.gradle.org/current/userguide/dependency_versions.html

I think we can use https://github.com/ben-manes/gradle-versions-plugin + https://github.com/kevcodez/gradle-upgrade-interactive to make it easier for us. I'm against these automatic pr's trough. At least when it doesn't combine multiple updates in one pr.

@Zoriot Zoriot marked this pull request as draft May 24, 2026 21:09
Zoriot added 3 commits June 7, 2026 23:53
…cies.

This was done automatically via the littlerobots/version-catalog-update-plugin.
- add Java toolchain configuration via Gradle properties
- add Paper-next dependency constraints
- add buildPaperNext verification task
- support compiling against Java 25 and Paper 1.26
@Zoriot Zoriot marked this pull request as ready for review June 7, 2026 22:47

@Cinnazeyy Cinnazeyy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@Cinnazeyy

Copy link
Copy Markdown
Member

im fine with using a version range for paper as long as that range is limited to the current major minecraft version that we want to target. (so only updates for paper patches). im not too worried about reproducibility for that.
as for the rest of our libraries and plugins, i think it would probably be better to stick with the specific versions, as that could get messy real quick

@Zoriot Zoriot merged commit 145d5b7 into main Jun 8, 2026
2 checks passed
@Zoriot Zoriot deleted the updates branch June 8, 2026 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants