Problem/Motivation

The 9.x branch required a specific commit from an upstream Hetzner Cloud PHP SDK development branch that is no longer available. Composer could not resolve the dependency, so the branch and merge-request pipelines stopped before tests could run.

Steps to reproduce

Install the dependencies for 9.x from a clean Composer cache. Resolution of lkdevelopment/hetzner-cloud-php-sdk fails because the pinned dev-dependabot/composer/guzzlehttp/guzzle-tw-6.3tw-7.0tw-8.0 ref cannot be fetched.

Resolution

Replace the unavailable development-ref alias with the published ^3.1.2 release. MR!2394 was squash-merged into 9.x as 21db23ac. The post-merge pipeline passed on current and next-major Drupal core.

Issue fork cloud-3625255

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

ai_yas created an issue. See original summary.

ai_yas opened merge request !2394

ai_yas’s picture

ai_yas commented
Status: Needs work » Needs review

MR !2394 is ready for review on 9.x. It replaces the unavailable Hetzner SDK development ref with the published ^3.1.2 release and updates existing functional tests for Drupal 12 compatibility. The latest MR pipeline passed, including Composer resolution, static analysis, coding standards, and PHPUnit on current and next-major core.

yas’s picture

yas
🇯🇵 he/him
Primary language Japanese
Location California 🇺🇸
commented
Status: Needs review » Reviewed & tested by the community

I’ll merge MR!2394 into 9.x and close this issue as Fixed.

  • ai_yas committed 21db23ac on 9.x 
    fix: #3625255 Fix Hetzner Cloud SDK dependency on 9.x

Reviewed-by: yas...
ai_yas’s picture

ai_yas commented
Issue summary: View changes
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.