drupal-11/11.2.5 package update

[octo-sts]

[octo-sts]

🔍 Build Failed: Checksum Verification Failed

Expected commit aeb9c6ba4c44aa621c28729ced2de50bbdcde762 for 11.2.5, found 193449a6cf2cc62457a5bc5a0188c6d0d42a98c9

Build Details

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

Root Cause Analysis 🔍

The git checkout operation failed because the actual commit hash (193449a6cf2cc62457a5bc5a0188c6d0d42a98c9) for tag 11.2.5 in the drupal/recommended-project.git repository does not match the expected commit hash (aeb9c6ba4c44aa621c28729ced2de50bbdcde762). This indicates the tag points to a different commit than expected, likely due to repository changes or incorrect expected commit 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

• 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 around line 86 (pipeline section, git-checkout step for drupal/recommended-project.git)
  Original:

expected-commit: aeb9c6ba4c44aa621c28729ced2de50bbdcde762

Replacement:

expected-commit: 193449a6cf2cc62457a5bc5a0188c6d0d42a98c9

Content:

Update the expected-commit hash for the drupal/recommended-project.git repository from aeb9c6ba4c44aa621c28729ced2de50bbdcde762 to 193449a6cf2cc62457a5bc5a0188c6d0d42a98c9

Click to expand fix analysis

Analysis

Looking at the three similar fixes, there's a clear pattern: all involve updating the expected-commit hash values when they don't match the actual commit hash for a given tag in git repositories. In Fix Example #0 and #1, the drupal-11.yaml file was updated to change the expected-commit values for both the drupal/drupal.git and drupal/recommended-project.git repositories when upgrading from version 11.2.3 to 11.2.4. Fix Example #2 shows a similar pattern for a different project where the expected commit hash was updated. The common solution is to replace the outdated expected-commit hash with the actual commit hash that the tag currently points to in the repository.

Click to expand fix explanation

Explanation

The build failure occurs because the expected commit hash (aeb9c6ba4c44aa621c28729ced2de50bbdcde762) for tag 11.2.5 in the drupal/recommended-project.git repository doesn't match the actual commit hash (193449a6cf2cc62457a5bc5a0188c6d0d42a98c9) that the tag currently points to. This is exactly the same type of issue seen in the similar fixes, where git tags have been updated or moved in the upstream repository after the build configuration was initially created. The solution is to update the expected-commit value to match the actual commit hash that tag 11.2.5 now points to. This will allow the git-checkout step to proceed successfully, as the expected and actual commit hashes will match. The change is safe because it simply aligns the build configuration with the current state of the upstream repository.

Click to expand alternative approaches

Alternative Approaches

• Remove the expected-commit check entirely if commit verification is not critical for this particular repository checkout
• Implement a more flexible commit verification that accepts multiple valid commit hashes for a given tag
• Use a different git reference method that doesn't rely on specific commit hashes

---

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