Problem/Motivation

Last week, Drupal 11 became the default ("current") version in GitLab CI. As a result, we need to update the CI config to keep testing on Drupal 10 (since it is now the "previous major"). "next major" currently has no effect because Drupal 12 doesn't have an active test branch, but I left it in and added "next minor" to test future versions of Drupal 11.

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:

Comments

ptmkenny created an issue. See original summary.

ptmkenny’s picture

Status: Active » Needs review
ptmkenny’s picture

Even though the test is failing, I think this should be committed because, by adding a test, it shows that the tests are failing.

alexpott made their first commit to this issue’s fork.

alexpott’s picture

I think we should allow the next minor to fail... we still get the info.

alexpott’s picture

Actually if we release an 11.x compatible version we need to say we conflict with 11.1.x because we already know we do - therefore this is going to fail hard. Not sure what to do. ick.

ptmkenny’s picture

Yeah, allowing failure makes sense; I made this MR before I realized how hard 11.1 compatibility was going to be.

I've updated the MR to block installation on 11.1 for now. I definitely think there should be an 11.0-compatible release, and hopefully an 11.1-compatible release to follow shortly after.

alexpott’s picture

alexpott’s picture

Status: Needs review » Reviewed & tested by the community

  • alexpott committed 15389a66 on 3.2.x authored by ptmkenny
    Issue #3482361 by ptmkenny, alexpott: Update GitLab CI config now that...
alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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