Adding VersionStream for gitlab-runner-18.8

[octo-sts]

No description provided.

[octo-sts]

🔄 Build Failed: Git Checkout Error

fatal: Remote branch v18.8.1 not found in upstream origin

Build Details

Category	Details
Build System	melange
Failure Point	git clone --quiet --origin=origin --config=user.name=Melange Build --config=user.email=melange-build@cgr.dev --config=advice.detachedHead=false --branch=v18.8.1 --depth=1 https://gitlab.com/gitlab-org/gitlab-runner

Root Cause Analysis 🔍

The git checkout step failed because the specified tag 'v18.8.1' does not exist in the remote GitLab repository. The build system attempted to clone with --branch=v18.8.1 but the remote repository does not have this tag available, causing git to exit with status 128.

---

🔍 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 gitlab-pages-18.5 #69386

Suggested Changes

File: gitlab-runner-18.8.yaml

• modification at line 31 (pipeline[0].uses.git-checkout.with.tag)
  Original:

tag: v${{package.version}}

Replacement:

tag: v${{package.version}}

Content:

The tag parameter should reference the full semantic version which is already correctly set as v18.8.1 through package.version

Click to expand fix analysis

Analysis

The similar fixes show a consistent pattern: when a git checkout fails with "Remote branch vX.Y not found", it's because the GitLab Runner package is trying to checkout a non-existent tag. In all three cases, the fixes involved creating new YAML files for the specific version (18.5) that was missing. The pattern shows that GitLab releases follow a semantic versioning scheme where tags like v18.5.0 exist but v18.5 does not. The fixes all use the full semantic version (e.g., v18.5.0) instead of the shortened version (v18.5) in the git-checkout tag parameter.

Click to expand fix explanation

Explanation

The current build failure occurs because the git checkout is trying to find tag 'v18.8.1' which doesn't exist in the GitLab Runner repository. Looking at the similar fixes, they all handled version 18.5 by ensuring the correct tag format and version alignment. The issue is likely that v18.8.1 simply doesn't exist as a tag in the GitLab Runner repository yet, or the expected-commit hash is incorrect for the version being requested. The solution is to verify that the tag v18.8.1 actually exists in the upstream repository and that the expected-commit hash (1c855082f3c308de9ac1dd087202b611f4b9d368) corresponds to that tag. If the tag doesn't exist, the package version should be updated to match an existing tag, or we should wait for the upstream release.

Click to expand alternative approaches

Alternative Approaches

• Check if v18.8.0 exists and downgrade the package version to 18.8.0 if v18.8.1 hasn't been released yet
• Remove the expected-commit requirement temporarily to see if the tag exists but with a different commit hash
• Use the latest available tag from the v18.8 series that actually exists in the repository

---

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