drupal-11/11.2.0 package update

[octo-sts]

[octo-sts]

🔄 Build Failed: Git Checkout Error

FAIL Expected commit fd3b0413407205068f7d571e5a70bdd84d377d4f for 11.2.0, found 338d58439d5b59d92ac9519ad81ffd916b673841

Build Details

Category	Details
Build System	melange
Failure Point	git checkout for drupal-11 package

Root Cause Analysis 🔍

The git checkout step expected a specific commit hash (fd3b0413407205068f7d571e5a70bdd84d377d4f) for tag 11.2.0, but found a different commit hash (338d58439d5b59d92ac9519ad81ffd916b673841). This mismatch between the expected and actual commit hash for the tag caused the build to fail.

---

🔍 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-runner-17.11 #51032
• gitlab-runner-17.10/17.10.1 package update #48261
• trufflehog/3.88.16-r0: cve remediation #46217

Suggested Changes

File: drupal-11.yaml

• replace at line 103 (pipeline.git-checkout.expected-commit)
  Original:

      expected-commit: fd3b0413407205068f7d571e5a70bdd84d377d4f

Replacement:

      expected-commit: 338d58439d5b59d92ac9519ad81ffd916b673841

Content:

Update the expected commit hash to match the actual commit hash for Drupal 11.2.0 tag

Click to expand fix analysis

Analysis

After analyzing the similar fixed build failures, a clear pattern emerges: all of these failures involve a mismatch between the expected commit hash and the actual commit hash found when checking out a specific tag. In each case, the fix was to update the expected-commit parameter in the git-checkout step to match the actual commit hash that the tag points to.

The current build failure shows the same pattern - the expected commit hash (fd3b0413407205068f7d571e5a70bdd84d377d4f) doesn't match the actual commit hash (338d58439d5b59d92ac9519ad81ffd916b673841) for the Drupal 11.2.0 tag. This occurs because git tags can be changed or updated by the repository maintainers, causing the commit they point to to change.

Click to expand fix explanation

Explanation

The build is failing because the git-checkout step in the Melange YAML file is expecting the Drupal 11.2.0 tag to point to commit fd3b0413407205068f7d571e5a70bdd84d377d4f, but in reality, it points to commit 338d58439d5b59d92ac9519ad81ffd916b673841.

This mismatch can happen for several reasons:

1. The upstream repository maintainers may have moved the tag to a different commit
2. The tag might be an annotated tag (which points to a tag object, not directly to a commit)
3. The tag might have been force-updated with a different commit

The fix is straightforward - update the expected-commit value to match the current commit hash that the tag points to. This approach matches what was done in all three similar fixed build failures, where in each case the expected-commit hash was updated to match the actual commit hash of the tag.

After making this change, the git-checkout step should succeed because the expected commit hash will now match the actual commit hash for the Drupal 11.2.0 tag.

Click to expand alternative approaches

Alternative Approaches

• Instead of hardcoding the commit hash, modify the pipeline to detect and use the actual commit hash that the tag points to. This would require adding a script that resolves the tag to a commit hash before the git-checkout step.
• Remove the expected-commit check entirely, which would allow checking out whatever commit the tag currently points to. However, this would remove a security feature that ensures the code being built matches what was expected.
• Pin to a specific commit instead of a tag, which would provide more stability but would require manual updates for each new version.

---

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

[octo-sts]

superseded by #57516