drupal-11/11.2.2 package update

[octo-sts]

[octo-sts]

🔄 Build Failed: Git Checkout Error

FAIL Expected commit 4a1db0db3b144a42daa0887e904f942a55fe5b6b for 11.2.2, found 965123445745f50c7fc001c72a96650518c267d2

Build Details

Category	Details
Build System	git
Failure Point	git checkout

Root Cause Analysis 🔍

The build failed because the actual commit hash for Drupal tag 11.2.2 (965123445745f50c7fc001c72a96650518c267d2) does not match the expected commit hash specified in the build configuration (4a1db0db3b144a42daa0887e904f942a55fe5b6b). This indicates that either the tag has been updated in the repository since the build configuration was created, or there's an incorrect commit hash specified in the 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
• Improve Trino package #51354
• fontconfig/2.16.1 package update #46365

Suggested Changes

File: drupal-11.yaml

• replace at line pipeline section, git-checkout with repository: https://github.com/drupal/drupal.git (pipeline.git-checkout)
  Original:

      expected-commit: 4a1db0db3b144a42daa0887e904f942a55fe5b6b

Replacement:

      expected-commit: 965123445745f50c7fc001c72a96650518c267d2

Content:

Update the expected-commit hash to match the actual commit hash for Drupal 11.2.2

Click to expand fix analysis

Analysis

After examining the similar fixed build failures, a clear pattern emerges: all three examples involved fixing a Git commit hash mismatch in the expected-commit parameter of the git-checkout action. In each case, the build failed because the actual commit hash for a specific tag didn't match what was specified in the configuration. The fixes consistently involved updating the expected-commit value to match the actual commit hash that the tag points to in the upstream repository. This suggests that tags in Git repositories sometimes get updated to point to different commits, particularly when tags are annotated objects rather than direct references to commits.

Click to expand fix explanation

Explanation

The build is failing because the expected commit hash for Drupal tag 11.2.2 (4a1db0db3b144a42daa0887e904f942a55fe5b6b) doesn't match the actual commit hash (965123445745f50c7fc001c72a96650518c267d2) that the tag points to in the repository. This could happen for several reasons:

1. The tag may have been updated in the upstream repository since the build configuration was created
2. The tag might be an annotated tag object rather than a direct reference to a commit
3. The repository structure may have changed or been reorganized

By updating the expected-commit value in the git-checkout action to match the actual commit hash (965123445745f50c7fc001c72a96650518c267d2), we're telling the build system to expect that specific commit when checking out the 11.2.2 tag, which should resolve the mismatch error.

This solution directly addresses the error message "FAIL Expected commit 4a1db0db3b144a42daa0887e904f942a55fe5b6b for 11.2.2, found 965123445745f50c7fc001c72a96650518c267d2" by updating our expectation to match reality.

Click to expand alternative approaches

Alternative Approaches

• Rather than updating the expected commit hash, we could consider using a different Git checkout option that doesn't validate the commit hash. However, this would reduce security as the hash validation helps ensure the code integrity.
• Another approach would be to check out the specific commit hash directly rather than using the tag. However, this would make future version updates more complex and less automated.
• We might need to also update the expected commit for the recommended-project repository checkout as it's using the same hash. If both repositories should be in sync, updating both expected-commit values would be necessary.

---

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

[aborrero]

LGTM.