Skip to content

Show the build name as the plugin version - #180

Merged
Travja merged 1 commit into
devfrom
claude/dev-build-names
Oct 27, 2026
Merged

Travja merged 1 commit into
devfrom
claude/dev-build-names

Conversation

@Travja

@Travja Travja commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator

Part of giving every dev build a name users can share, X.Y.Z-dev.N. The shared workflow (.github patch 0011) numbers each dev build, tags it and publishes it as a GitHub pre-release, and passes the name to Maven as -Ddisplay.version.

Changes

  • plugin.yml, paper-plugin.yml, bungee.yml: version: ${display.version}.
  • Root pom.xml: display.version defaults to ${project.version}, so local builds are unchanged, and CI sets it to 1.2.1-dev.1 or 1.2.1. The Maven version stays X.Y.Z-SNAPSHOT, so Fabled and Divinity keep following the latest dev build.

With this, /version Codex on a server shows e.g. 1.2.1-dev.3. That's also the tag and GitHub pre-release the build can be downloaded from. Fabled's and Divinity's minimum-Codex check now orders these correctly (magemonkeystudio/fabled#1894, magemonkeystudio/divinity#356).

Testing

mvn package -DskipNms (JDK 25):

Build plugin.yml / paper-plugin.yml bungee.yml
defaults 1.2.0-SNAPSHOT 1.2.0-SNAPSHOT
-Drevision=1.2.1 -Dchangelist=-SNAPSHOT -Ddisplay.version=1.2.1-dev.1 1.2.1-dev.1 1.2.1-dev.1
-Drevision=1.2.1 -Dchangelist= 1.2.1 1.2.1

Generated by Claude Code

plugin.yml, paper-plugin.yml and bungee.yml now show ${display.version}, which
defaults to the project version. CI sets it to the build's name, X.Y.Z-dev.N for
a dev build or X.Y.Z for a release, so users can say exactly which build they run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Secz6aiBJ7U8im8tnYhyLA
@Travja Travja added the build:patch label Oct 27, 2026 — with Claude
@Travja
Travja merged commit bcf0cb1 into dev Oct 27, 2026
2 of 3 checks passed
@Travja
Travja deleted the claude/dev-build-names branch October 27, 2026 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants