>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3463894. --> Reported by: [berdir](https://www.drupal.org/user/214652) Related to !242 !246 !249 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Make Drupal 11 be the default/current option when running tests.<br> The MR is ready but we will wait a few _weeks_ until we make the change. See the rest of the description and initial comments for more details</p> <h3>Todo - Technical tasks</h3> <ul> <li>&#9989; Update variables so D11 is current and D10 is previous major</li> <li>&#9989; Decide if <code>.amend-core-requirements-drupal-11</code> is needed and where. Yes, but deprecate this name and replace with a generic <code>amend-core-requirements-next-major</code></li> <li>&#9989; <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/gitlab_templates/issues/3447792" title="Status: Closed (fixed)">#3447792: Add _TARGET_PHP_IMAGE_VARIANT to cater for newer sqlite versions for Drupal 11</a></span></li> <li>&#9989; <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/gitlab_templates/issues/3414505" title="Status: Closed (fixed)">#3414505: Allow all sub-modules to be compatible with next_major</a></span></li> <li>&#9989; All downstream pipelines should be green with the new variables.</li> <li>&#9989; <strong>Step 2 blocker</strong>: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/gitlab_templates/issues/3458238" title="Status: Closed (fixed)">#3458238: CI installs wrong Drupal version</a></span> (merged)</li> <li>&#9989; <strong>Step 2 blocker</strong>: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/gitlab_templates/issues/3462681" title="Status: Closed (fixed)">#3462681: Add W3C compliant JS testing</a></span> (merged)</li> </ul> <h3>Todo - Actions</h3> <ul> <li>&#9989; Publish a DA blog post about the big full change-over (suggested by @larowlan - <a href="https://drupal.slack.com/archives/CGKLP028K/p1722803135150269?thread_ts=1722796036.303819&amp;cid=CGKLP028K">https://drupal.slack.com/archives/CGKLP028K/p1722803135150269?thread_ts=1722796036.303819&amp;cid=CGKLP028K</a>)</li> <li>&#9989; A draft for the blog post can be read in <a href="https://git.drupalcode.org/issue/gitlab_templates-3463894/-/blob/e6c600c5a4d1b1881916b1e0bfb23497664c5f89/draft-announcement.md">draft-announcement.md</a></li> <li>&#9989; The <a href="https://www.drupal.org/drupalorg/blog/gitlab-ci-templates-will-make-drupal-11-the-default-version-to-run">blog post</a> was published 21 August</li> <li>&#9989; Announce this to contrib via slack as well, once the blog post is published</li> <li>&#9989; Initially change <code>OPT_IN_TEST_NEXT_MAJOR</code> default to 1, set 'Composer Next Major' to be allowed to fail (and no other changes) and release 1.5.6, so that Contrib automatically start testing at D11</li> <li>&#9989; Step 1 (<a href="https://git.drupalcode.org/project/gitlab_templates/-/merge_requests/246">MR246</a>) was merged on 26 August, and <code>1.5.6</code> released and <code>default-ref</code> updated</li> <li>&#9989; Other issues were found and fixed, and the latest release with D10 as "current" is now <code>1.5.9</code></li> <li>&#9989; Step 2 - on <del>7th</del> 8th October merge <a href="https://git.drupalcode.org/project/gitlab_templates/-/merge_requests/242">MR242</a> but only in 'main' ref, no update to 'default-ref'. Release <code>1.6.0</code></li> <li>&#9989; Some more issues found and fixed, improved support documentation. <code>1.6.3</code> is the latest tag, but default-ref is still <code>1.5.10</code> which will be the last "D10 is current" tag</li> <li>&#9989; Step 3 - on <del>14th</del> 15th October update the default ref to match <code>1.6.3</code> so that this change goes to all Contrib</li> </ul> <hr> Keeping the original description for context: <p>I brought this up a while ago in a slack thread, posting it here to make it a bit more official as a request.</p> <p>While contrib is catching up quite nicely to D11, lots are still not compatible with D11 and many of my projects that are rely on workarounds to be able to run D11 tests, lenient, using sed to force development dependencies to be D11 compatible and so on.</p> <p>Arguments:<br> * Switching to 11.0 as current version will interrupt contribution workflows as pipelines will fail for those projects that aren't compatible yet and also those that rely on "next major" job customizations to make it work. Some projects will not be able to be D11 compatible for an extended timeframe even, for example simplesamlphp_auth, due to dependency conflicts with the simplesamlphp and symfony projects.<br> * There won't be a next next major for quite some time, we don't need to free up the current next major jobs for that. not 100% sure about implications on next minor.<br> * The templates aren't really ready yet to account for the fact that some combinations won't be valid, like there won't be a previous minor with 11.0: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/gitlab_templates/issues/3426289" title="Status: Closed (fixed)">#3426289: Cater for empty next/previous minor/major when it's not possible</a></span><br> * Drupal 10 is an LTS release, it will be around for quite some time and most modules will want to remain compatible with that. That's more a long-term thing, but testing on D10 will ensure that new changes don't accidentally introduce dependencies on new D11 features. Accidentally breaking forward compatibility seems less likely IMHO.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Either just postpone the switch for a few weeks at least to give contrib time to catch up or alternatively consider making the switch to D11 opt-in, with a variable if that's possible or a different branch. I suppose that's possible disabling current testing and enable previous major, but that's more of an opt-out than an opt-in.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3> > Related issue: [Issue #3426289](https://www.drupal.org/node/3426289) > Related issue: [Issue #3444714](https://www.drupal.org/node/3444714) > Related issue: [Issue #3447792](https://www.drupal.org/node/3447792) > Related issue: [Issue #3458238](https://www.drupal.org/node/3458238) > Related issue: [Issue #3429812](https://www.drupal.org/node/3429812) > Related issue: [Issue #3462681](https://www.drupal.org/node/3462681) > Related issue: [Issue #3479160](https://www.drupal.org/node/3479160)