Update CI workflows for Drupal 11 switch

Can’t we for now pin to a GitLab CI template tag/version? 🤔

Per https://www.drupal.org/drupalorg/blog/gitlab-ci-templates-will-make-drup... →

All blockers for Step 3 are now fixed. The release that will be made default is 1.6.3, which contains issues fixed between steps 1 and 3.

So let's just pin to 1.6.2 for now.

1.6.2 didn't work, trying 1.5.x instead.

Wow, the switch happened today (October 15, 2024) as was announced at https://www.drupal.org/drupalorg/blog/gitlab-ci-templates-will-make-drup... → . Too bad it's causing this much disruption, and especially too bad that there's no regard for semantic versioning at all 😳

This is hard-blocking 📌 Add PHP test coverage of layout controller Active and any/all other MRs, so the one-line change in https://git.drupalcode.org/project/experience_builder/-/merge_requests/365 to pin to 1.5.x of the GitLab CI Templates is definitely preferable.

We need a follow-up, but we also need to ASAP unblock development work.

P.S.: This reminds me of the fact that we originally were running Cypress on both 10.x and 11.x, but then at some point we couldn't get that to work reliably. That's why we've been running the Cypress E2E tests specifically on 10.x only for months now!

wim leers → closed merge request !364

Follow-up created: 📌 CI: update to 1.6.3 of the GitLab CI Template Active .

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