Adding VersionStream for gitaly-18.8

[octo-sts]

No description provided.

[octo-sts]

🔍 Build Failed: Checksum Verification Failed

Expected commit effe3c47a73ff0bdc30008ae76dd43707caca97d for v18.8.1, found 7f9f51ad10c67df47dd6f36ef5c8ebf2eb4cd325

Build Details

Category	Details
Build System	melange
Failure Point	git checkout step during package build - git tag verification failed

Root Cause Analysis 🔍

The git tag v18.8.1 points to a different commit hash than expected. The build process expected commit effe3c47a73ff0bdc30008ae76dd43707caca97d but found 7f9f51ad10c67df47dd6f36ef5c8ebf2eb4cd325. This indicates either the tag was moved/updated upstream, or there's a mismatch in the package configuration's expected commit hash.

---

🔍 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

• fix: wrong ldflags for gitlab agent casuing UI issues #63456
• Adding VersionStream for gitaly-18.3 #64066

Suggested Changes

File: gitaly-18.8.yaml

• modification at line 33 (pipeline git-checkout step)
  Original:

expected-commit: effe3c47a73ff0bdc30008ae76dd43707caca97d

Replacement:

expected-commit: 7f9f51ad10c67df47dd6f36ef5c8ebf2eb4cd325

Content:

Update the expected-commit hash to match the actual commit that tag v18.8.1 points to

Click to expand fix analysis

Analysis

All three similar fixes follow the same pattern: when a git tag points to a different commit than expected, the solution is to update the expected-commit field in the git-checkout step to match the actual commit hash that the tag currently points to. In Fix Example #0, the expected-commit was updated from 88f979d79bb1c74f98c9ae0720dcc5eb6f83371c to b7cdc2ac78f7dabac1f9312ee96b6dedaf91171f. In Fix Example #1, it was updated from 1c82a19884b61c6d7158f9d78b14d31286ccc59d to aa1b6f9f80359df0a30cfca92646227ee5acdf2e. In Fix Example #2, it was updated from 3e6926ff6ed2dd5ee8a11b9bd42174f29a71cea3 to cf69fd6c2c8e0af90cfa010cacd12f00f61e1cf6. This pattern indicates that upstream repositories occasionally move or update tags, requiring the build configuration to be updated with the correct commit hash.

Click to expand fix explanation

Explanation

This fix addresses the root cause of the build failure by updating the expected-commit hash to match the actual commit that the v18.8.1 tag points to in the upstream repository. The error indicates that the tag v18.8.1 currently points to commit 7f9f51ad10c67df47dd6f36ef5c8ebf2eb4cd325, but the build configuration expects effe3c47a73ff0bdc30008ae76dd43707caca97d. This mismatch causes the git-checkout verification to fail. By updating the expected-commit field to the correct hash, the build process will be able to successfully checkout and verify the correct commit for the v18.8.1 tag. This is the standard approach used in all similar fixes and ensures that the build uses the exact commit that upstream has tagged for this version.

Click to expand alternative approaches

Alternative Approaches

• Remove the expected-commit field entirely to allow the build to accept whatever commit the tag points to, though this reduces security verification
• Investigate if the upstream repository has multiple tags or if there was a force-push that changed the tag, and potentially use a different tag or commit reference
• Contact upstream maintainers to understand why the tag was moved, in case this indicates a security issue or incorrect tagging

---

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