drupal-11/11.2.8 package update

[octo-sts]

Commit: f8bdd0862798ad59a8ebf87fb1df69642b799f5a

[octo-sts]

🔄 Build Failed: Git Checkout Error

Expected commit f8bdd0862798ad59a8ebf87fb1df69642b799f5a for 11.2.8, found 413ca92a74d9a0a5dcb47005f176d17f5a6f5f9a

Build Details

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

Root Cause Analysis 🔍

Git checkout operation failed because the actual commit hash (413ca92a74d9a0a5dcb47005f176d17f5a6f5f9a) for tag 11.2.8 in the drupal/recommended-project.git repository does not match the expected commit hash (f8bdd0862798ad59a8ebf87fb1df69642b799f5a). This indicates a mismatch between what the build configuration expects and what exists in the repository.

---

🔍 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

• update at line 81 (pipeline section, first git-checkout step)
  Original:

expected-commit: f8bdd0862798ad59a8ebf87fb1df69642b799f5a

Replacement:

expected-commit: 413ca92a74d9a0a5dcb47005f176d17f5a6f5f9a

Content:

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

• update at line 87 (pipeline section, second git-checkout step)
  Original:

expected-commit: f8bdd0862798ad59a8ebf87fb1df69642b799f5a

Replacement:

expected-commit: 413ca92a74d9a0a5dcb47005f176d17f5a6f5f9a

Content:

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

Click to expand fix analysis

Analysis

Looking at the similar fixed build failures, there's a clear pattern: all three fixes involved updating the expected-commit hash to match the actual commit hash found in the repository for the corresponding tag. In each case, the tag existed but pointed to a different commit than what was expected in the build configuration. The fixes involved: 1) Updating the package version to the new target version, and 2) Updating the expected-commit field(s) to match the actual commit hash that the tag points to in the upstream repository. The current failure shows the same pattern - tag 11.2.8 exists but points to commit 413ca92a74d9a0a5dcb47005f176d17f5a6f5f9a instead of the expected f8bdd0862798ad59a8ebf87fb1df69642b799f5a.

Click to expand fix explanation

Explanation

This fix should work because the error indicates that tag 11.2.8 exists in both repositories but points to commit 413ca92a74d9a0a5dcb47005f176d17f5a6f5f9a rather than the expected f8bdd0862798ad59a8ebf87fb1df69642b799f5a. This is a common scenario where upstream repositories have updated or re-tagged releases, causing the commit hash to change. By updating the expected-commit values to match the actual commit hash that the tag currently points to, the git-checkout operations will succeed. The pattern from all similar fixes shows this is the standard resolution - the build configuration needs to be updated to reflect the current state of the upstream repositories. Since both git-checkout steps in the pipeline are failing with the same commit mismatch, both need to be updated to the new commit hash.

Click to expand alternative approaches

Alternative Approaches

• Verify the tag 11.2.8 actually exists and contains the expected Drupal 11.2.8 release by manually checking the upstream repositories before applying the fix
• Consider using a more flexible approach like removing the expected-commit constraint entirely if the upstream frequently re-tags releases, though this reduces build reproducibility
• Check if there are separate tags for the drupal/drupal.git and drupal/recommended-project.git repositories that might have different commit hashes and update them accordingly

---

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

[OddBloke]

This package has been removed.