drupal-11/11.2.3 package update

[octo-sts]

[octo-sts]

🔄 Build Failed: Git Checkout Error

FAIL Expected commit 0bf2e9cf405162e4ba3f7611f868efdc468e340c for 11.2.3, found 0edd16b94cff9cc21e3a501c9b0222364791008a

Build Details

Category	Details
Build System	melange
Failure Point	git checkout step for drupal/recommended-project.git repository

Root Cause Analysis 🔍

The git checkout operation failed because the expected commit hash (0bf2e9cf405162e4ba3f7611f868efdc468e340c) for tag 11.2.3 in the drupal/recommended-project repository does not match the actual commit hash found (0edd16b94cff9cc21e3a501c9b0222364791008a). This indicates a mismatch between the expected and actual state of the repository at the specified tag, likely due to repository changes or incorrect expected commit configuration in the build configuration.

---

🔍 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

Suggested Changes

File: drupal-11.yaml

• modification at line 77 (pipeline section, second git-checkout step)
  Original:

expected-commit: 0bf2e9cf405162e4ba3f7611f868efdc468e340c

Replacement:

expected-commit: 0edd16b94cff9cc21e3a501c9b0222364791008a

Content:

Update the expected-commit hash for the drupal/recommended-project.git repository to match the actual commit hash that tag 11.2.3 points to

Click to expand fix analysis

Analysis

The similar fixed build failures all follow the same pattern: git tag commit hash mismatches where the expected-commit value in the build configuration doesn't match the actual commit hash that the git tag points to in the repository. In all three cases, the fix was to update the expected-commit value to match the actual commit hash found in the repository. This indicates that either the git tags were moved/updated upstream, or the initial expected-commit values were incorrect. The pattern shows that the solution is straightforward: replace the incorrect expected-commit hash with the correct one that the tag actually points to.

Click to expand fix explanation

Explanation

The build failure is caused by a mismatch between the expected commit hash (0bf2e9cf405162e4ba3f7611f868efdc468e340c) and the actual commit hash (0edd16b94cff9cc21e3a501c9b0222364791008a) that the git tag 11.2.3 points to in the drupal/recommended-project repository. This is exactly the same type of issue seen in all three similar fixes. The solution is to update the expected-commit value to match the actual commit hash that the tag references. This fix will allow the git-checkout operation to succeed because the expected and actual commit hashes will match. The first git-checkout for drupal/drupal.git uses the same expected-commit value, but since the error specifically mentions drupal/recommended-project.git, we only need to update the second git-checkout step.

Click to expand alternative approaches

Alternative Approaches

• Remove the expected-commit parameter entirely from the git-checkout step, which would allow any commit that the tag points to without validation
• Verify both repositories use the same commit hash for the same tag and update both if they differ
• Use a different tag or branch if the current tag 11.2.3 is pointing to an unexpected commit due to upstream changes

---

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