Skip to content

fix: build releases as the stable branch - #13

Merged
ryanbarlow97 merged 1 commit into
masterfrom
fix/release-branch-4fec1582
Sep 23, 2026
Merged

ryanbarlow97 merged 1 commit into
masterfrom
fix/release-branch-4fec1582

Conversation

@ryanbarlow97

Copy link
Copy Markdown
Contributor

Release builds set <project.branch>development</project.branch>, which plugin.yml exposes as branch. VersionUtils.getBranch() turns that into -development, and Patch.java (around line 247) skips every database patch script when the edition branch contains -dev. On an existing 24.0 database, v25.0.0 therefore never applies the 2.25.0 upgrade: the new message-search indexes are missing, and on MySQL entity.data is not widened.

This clears the property, matching upstream stable releases, so the upgrade runs on first start after an upgrade from 24.0. The value was introduced in 5525a82 and nothing else reads it.

Validation: project.branch is only referenced by plugin.yml; an empty value makes getBranch() return an empty string. The standard build must pass before merge.

🤖 Generated with Claude Code

The development branch value made release builds report a -development
edition, so Patch skipped the database upgrade scripts on existing
databases. Release builds now carry an empty branch, matching upstream
stable releases, so the 2.25.0 upgrade runs on first start.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@ryanbarlow97
ryanbarlow97 merged commit 1fca016 into master Sep 23, 2026
1 check passed
@ryanbarlow97
ryanbarlow97 deleted the fix/release-branch-4fec1582 branch September 23, 2026 09:10
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.

1 participant