Adding VersionStream for clickhouse-25.12

[octo-sts]

No description provided.

[octo-sts]

⚙️ Build Failed: Configuration

unable to parse version '25.12.1.649-stable' for clickhouse-25.12.yaml: invalid version 25.12.1.649-stable, could not parse

Build Details

Category	Details
Build System	melange
Failure Point	melange package version parsing for clickhouse-25.12.yaml

Root Cause Analysis 🔍

The version string '25.12.1.649-stable' does not conform to melange's expected semantic versioning format. The '-stable' suffix is not a valid semantic version identifier, and the version parser cannot handle this format.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• Adding VersionStream for clickhouse-25.11 #73569
• Adding VersionStream for clickhouse-25.10 #71201

Suggested Changes

File: clickhouse-25.12.yaml

• modification at line 3 (package.version field)
  Original:

version: "25.12.1.649-stable"

Replacement:

version: "25.12.1.649"

Content:

Remove the '-stable' suffix from the package version to make it compatible with semantic versioning requirements

Click to expand fix analysis

Analysis

All three similar fixed build failures share the exact same issue: the version string contains a '-stable' suffix that makes it incompatible with melange's semantic versioning parser. In each case, the fix was identical - the package version was changed from including the '-stable' suffix (e.g., '25.11.1.558-stable') to excluding it (e.g., '25.11.1.558'). The git checkout configuration was then modified to handle the upstream tag format by using 'strip-suffix: -stable' in the update section, which allows the build system to properly map the clean semantic version to the correct upstream git tag.

Click to expand fix explanation

Explanation

This fix addresses the root cause of the version parsing failure by removing the '-stable' suffix that melange's semantic version parser cannot handle. The version '25.12.1.649' is a valid semantic version that melange can parse, while '25.12.1.649-stable' is not because '-stable' is not a valid pre-release identifier according to semantic versioning standards. The existing 'strip-suffix: -stable' configuration in the update section already handles the mapping between the clean package version and the upstream git tags (v25.12.1.649-stable), so no other changes are needed. This approach maintains compatibility with the upstream repository structure while ensuring melange can properly parse the version string.

Click to expand alternative approaches

Alternative Approaches

• Use a different version format like '25.12.1.649+stable' with a build metadata suffix, though this would require updating the git checkout tag reference
• Implement custom version transformation logic in melange, but this would be a much more complex change affecting the build system itself
• Use epoch bumping combined with a different versioning scheme, but this goes against the requirement to ignore epoch bump suggestions

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.