[Travja]

This is the same change as magemonkeystudio/divinity#349 and magemonkeystudio/fabled#1868. CI stops committing version bumps. The version is worked out at build time instead: the last release tag, bumped by the highest build:major/build:minor/build:patch label among the PRs merged since.

Changes

• Merges main into dev. This brings over 2390c03 (Clone ItemsAdder items on creation: ItemsAdderProvider.create() returns .clone()). That fix was only ever committed to main, so it's a real code change for dev. The merge also lets the monthly release fast-forward main.
• pom.xml: <version>${revision}${changelist}</version> plus flatten-maven-plugin.
  • codex-api, codex-core, codex-plugin and codex-bungee point their <parent> at the same expression.
  • The codex-nms modules keep their own fixed versions, as before (the old bump script skipped them too).
• devbuild.yml: weekly X.Y.Z-SNAPSHOT of dev on JDK 25 with -DskipNms (Mondays 12:17 UTC), skipped if nothing was committed that week. Can be run by hand.
• release.yml: monthly X.Y.Z release on JDK 25 with the BuildTools step and the nms profile. It runs on the 1st at 13:23 UTC, ahead of Fabled (14:53) and Divinity (15:23). It tags dev, deploys, creates a GitHub Release with codex-X.Y.Z.jar, and fast-forwards main.
• semver-label.yml: a PR into dev needs exactly one of build:major, build:minor or build:patch. The plain major/minor/patch labels Dependabot adds by itself are ignored. Dependabot PRs get build:patch.
• README: release and dev version badges next to the Release Build and Dev Build status badges. This also fixes the badge links, which pointed at magemonkeystudios.

Since #173 merged, this PR is merged up to it: pom-dev.xml is gone (the dev build uses -DskipNms instead), and both workflows pass java_version: '25'.

First release: 1.2.0

The last release is 1.1.1-R1, so with no labels the first release would be 1.1.2. That's below Divinity's MIN_CORE_VERSION (1.2.0-R0.7-SNAPSHOT), and Divinity would disable itself. I've put build:minor on #153, which adds new Compat API, so the first release is 1.2.0. That passes Divinity's and Fabled's version checks.

Before merging

• .github patch 0005 is applied. It adds the java_version input to reusable-semver-build.yml. Without it, both workflows here fail at startup with an unknown input. The same patch adds it to the old reusable-build.yml, which fixes the workflows Build on JDK 25, bump WorldEdit/WorldGuard, replace pom-dev.xml with a profile #173 left on dev.
• The .github patch that switches the shared workflows to build:* labels is applied.
• The shared workflows (reusable-semver-build.yml, reusable-semver-label.yml, actions/next-version) are in magemonkeystudio/.github main.
• The 15 tags from before April 2024 are deleted.
• The .github patch that runs BuildTools for 26.2/26.3 is applied.

After merging

• Make label / semver-label a required check on dev.
• Point Divinity's and Fabled's codex.version at a release or 1.2.0-SNAPSHOT. The R0.x-SNAPSHOT versions they use now won't get new builds.

Testing

• On Temurin 25, mvn package -DskipNms -Drevision=1.2.0 -Dchangelist=-SNAPSHOT (the dev build) builds all modules at 1.2.0-SNAPSHOT. codex-1.2.0-SNAPSHOT.jar (in ../build, where the release step picks it up) has version: 1.2.0-SNAPSHOT, and every module's flattened pom has the resolved parent version.
• With -P gpg,publish and no -DskipNms (the release build), the reactor includes the NMS modules and passes mvn validate. I didn't run a full release build because it needs the BuildTools jars.
• The version script on Codex's history picks 1.1.1-R1 as the last release and gives 1.2.0 with Add equipment-slot-scoped attribute modifier support to Compat #153 labeled build:minor.
• actionlint passes on the new workflows.

---

Generated by Claude Code