drupal-11/11.2.7 package update

[octo-sts]

[octo-sts]

🔄 Build Failed: Git Checkout Error

Expected commit ac4c930466bf508d12e26527ff67649a43de4e4c for 11.2.7, found dca14eef34aeaf6bc969b1f2893e5da3af1445fd

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 actual commit hash (dca14eef34aeaf6bc969b1f2893e5da3af1445fd) for tag 11.2.7 in the drupal/recommended-project repository does not match the expected commit hash (ac4c930466bf508d12e26527ff67649a43de4e4c). This indicates a mismatch between the expected and actual repository state, likely due to different commit histories between the main drupal/drupal repository and the drupal/recommended-project repository for the same tag version.

---

🔍 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

• drupal-11/11.2.4 package update #65239
• drupal-11/11.2.4 package update #65239

Suggested Changes

File: drupal-11.yaml

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

expected-commit: ac4c930466bf508d12e26527ff67649a43de4e4c

Replacement:

expected-commit: dca14eef34aeaf6bc969b1f2893e5da3af1445fd

Content:

Update the expected-commit hash for the drupal/recommended-project repository to match the actual commit hash found for tag 11.2.7

Click to expand fix analysis

Analysis

Looking at the three similar fixes, there's a clear pattern: when git checkout fails due to commit hash mismatches, the solution is to update the expected-commit values in the YAML file to match the actual commit hashes found in the repositories. In all cases, the fixes involved updating both the package version and the corresponding expected-commit hashes for the specific repositories. The pattern shows that different repositories (drupal/drupal vs drupal/recommended-project) can have different commit hashes for the same tag, which is expected since they are separate repositories with different histories.

Click to expand fix explanation

Explanation

The build failure occurs because the YAML file specifies the same expected-commit hash (ac4c930466bf508d12e26527ff67649a43de4e4c) for both the drupal/drupal repository and the drupal/recommended-project repository. However, these are separate repositories with different commit histories, so they will have different commit hashes for the same tag version. The error message indicates that for tag 11.2.7 in the drupal/recommended-project repository, the actual commit hash is dca14eef34aeaf6bc969b1f2893e5da3af1445fd, not the expected ac4c930466bf508d12e26527ff67649a43de4e4c. By updating the expected-commit value for the drupal/recommended-project checkout to match the actual commit hash, the build should proceed successfully. This follows the exact same pattern seen in all three similar fixes where the expected-commit values were updated to match the actual repository state.

Click to expand alternative approaches

Alternative Approaches

• Remove the expected-commit parameter entirely from the git-checkout step, which would allow any commit for the specified tag to be checked out without validation
• Verify the correct commit hash by manually checking the drupal/recommended-project repository for tag 11.2.7 and confirm the hash before updating
• Consider using a different approach like downloading release archives instead of git checkout if commit hash validation continues to be problematic

---

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

[OddBloke]

Closing in favour of #71625