Skip to content

Fix build artifacts for non-numeric Git tags - #848

Closed
YBronst wants to merge 6 commits into
CloverHackyColor:masterfrom
YBronst:master
Closed

YBronst wants to merge 6 commits into
CloverHackyColor:masterfrom
YBronst:master

Conversation

@YBronst

@YBronst YBronst commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Description

Fix build artifacts for non-numeric Git tags

Update the Clover build scripts to correctly handle both numeric and descriptive Git tags.

Previously, the build system assumed that the revision was always numeric and unconditionally added the r prefix. This resulted in incorrect artifact and installer version names for descriptive tags, for example:

Clover_rClover-Build-Alpha.pkg

The revision handling is now normalized as follows:

  • Numeric tags such as 5175 are converted to r5175.
  • Non-numeric tags such as Clover-Build-Alpha are used unchanged.
  • Composite tags such as Clover_r5200_Clover-Build-Alpha are also used unchanged.

This is applied consistently to:

  • Clover package names
  • CloverV2 archives
  • Clover ISO archives
  • Installer version information

Examples:

  • 5175 → Clover_r5175.pkg
  • Clover-Build-Alpha → Clover-Build-Alpha.pkg
  • Clover_r5200_Clover-Build-Alpha → Clover_r5200_Clover-Build-Alpha.pkg

This preserves the existing naming convention for numeric revisions while allowing descriptive Git tags to be used without generating duplicated or invalid r prefixes.

Type of change

  • Bugfix
  • New functionality
  • Code improvements
  • Documentation update

Checklist

  • Tested my changes locally
  • Added relevant comments to the code
  • Updated the relevant documentation

Additional information

Include any extra details relevant to your PR.

Fixed a bug where text-based Git tags
## Fix build artifacts for non-numeric Git tags

Update the Clover build scripts to correctly handle both numeric and descriptive Git tags.

Previously, the build system assumed that the revision was always numeric and unconditionally added the `r` prefix. This resulted in incorrect artifact and installer version names for descriptive tags, for example:

`Clover_rClover-Build-Alpha.pkg`

The revision handling is now normalized as follows:

* Numeric tags such as `5175` are converted to `r5175`.
* Non-numeric tags such as `Clover-Build-Alpha` are used unchanged.
* Composite tags such as `Clover_r5200_Clover-Build-Alpha` are also used unchanged.

This is applied consistently to:

* Clover package names
* CloverV2 archives
* Clover ISO archives
* Installer version information

Examples:

* `5175` → `Clover_r5175.pkg`
* `Clover-Build-Alpha` → `Clover-Build-Alpha.pkg`
* `Clover_r5200_Clover-Build-Alpha` → `Clover_r5200_Clover-Build-Alpha.pkg`

This preserves the existing naming convention for numeric revisions while allowing descriptive Git tags to be used without generating duplicated or invalid `r` prefixes.
Fix duplicate Clover prefix in CloverISO and CloverV2 archive names
@YBronst YBronst closed this Oct 7, 2026
@YBronst
YBronst deleted the master branch October 7, 2026 12:00
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