Adding VersionStream for clickhouse-26.1

[octo-sts]

No description provided.

[octo-sts]

⚙️ Build Failed: Configuration

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

Build Details

Category	Details
Build System	melange
Failure Point	Package version parsing during build configuration

Root Cause Analysis 🔍

The version string '26.1.2.11-stable' in the clickhouse-26.1.yaml configuration file does not conform to the expected semantic versioning format that melange can parse. The '-stable' suffix is likely causing the parsing failure as it's not a valid semantic version identifier.

---

🔍 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-26.1.yaml

• version_fix at line 3 (package section, line 3)
  Original:

  version: "26.1.2.11-stable"

Replacement:

  version: "26.1.2.11"

Content:

Remove the '-stable' suffix from the version string to make it compatible with melange's semantic version parser

Click to expand fix analysis

Analysis

All three similar build failures show the exact same issue: melange cannot parse version strings that contain the '-stable' suffix. In every case, the fix was to remove the '-stable' suffix from the package version field while keeping the git tag references intact. The pattern is consistent: change version from "X.Y.Z.W-stable" to "X.Y.Z.W" and ensure the update section has strip-suffix: -stable to handle future automated updates properly.

Click to expand fix explanation

Explanation

This fix will resolve the build failure because melange's version parser expects semantic versioning format (X.Y.Z or X.Y.Z.W) and cannot handle the '-stable' suffix. The '-stable' is not a valid pre-release identifier in semantic versioning. By removing it from the package version while keeping it in the git tag reference (v${{package.version}}-stable), the build will be able to parse the version correctly while still checking out the correct git tag. The update section already has 'strip-suffix: -stable' which ensures automated updates will work correctly by stripping this suffix when parsing new tags from upstream.

Click to expand alternative approaches

Alternative Approaches

• Use epoch bumping instead of changing version format - but this is not recommended as it doesn't address the root cause
• Modify melange to accept non-standard version formats - but this would require changes to the build system itself
• Use a different version numbering scheme - but this would deviate from upstream ClickHouse versioning

---

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