Skip to content

Include build number in mod metadata version for non-releases#223

Draft
Copilot wants to merge 1 commit intomaster-26from
copilot/add-build-number-to-mod-version
Draft

Include build number in mod metadata version for non-releases#223
Copilot wants to merge 1 commit intomaster-26from
copilot/add-build-number-to-mod-version

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 9, 2026

processResources was expanding ${mod_version} in mods.toml/neoforge.mods.toml/fabric.mod.json using the raw mod_version property (e.g. 1.25.5) rather than project.version, which already carries the build number suffix for non-releases (e.g. 1.25.5-944).

Change

  • buildSrc/src/main/groovy/multiloader-common.gradle: In processResources.expandProps, replace mod_version: mod_version with mod_version: project.version, so the full version string (including -<build_number> suffix) is written into mod metadata on CI builds, while tagged releases continue to produce the clean version.

Agent-Logs-Url: https://github.com/CyclopsMC/CyclopsCore/sessions/461a7190-337e-4568-ad30-f4345f80818b

Co-authored-by: rubensworks <440384+rubensworks@users.noreply.github.com>
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 9, 2026

@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 30.857%. remained the same — copilot/add-build-number-to-mod-version into master-26

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.

3 participants