5.x to require PHP 8.3 and >=10.3: bump requirements + fix deprecations

Wim Leers → credited Gábor Hojtsy → .

News since last time:

1. Drupal 11 requires PHP 8.3
2. PHP 8.1 support has been extended to December 31, 2025: https://www.php.net/supported-versions.php

I wrote 2.5 months ago:

So the choices are:

1. 5.x requiring PHP 8.2 and >=10.2, 6.x for >=11 requiring PHP 8.3
2. 5.x requiring PHP 8.3 and >=11, no 6.x any time soon

I think there's a 3rd option:

1. 5.x requiring PHP 8.3 and >=10.2, no 6.x any time soon

… that'll just mean that Tour support won't be available if you update to 5.x while still on Drupal 10.2.x But that's fine.

It'll still get us to where we need to be: a new major version that supports Drupal 11, will be around for the lifetime of Drupal 11, and is compatible with Drupal 10.x too (just not the first few minors).

Note that a 5.x version will be necessary anyway to support Drupal, see #3428342-5: Automated Drupal 11 compatibility fixes for cdn → .

Per #4.

Especially now that tests are green for 4.x on 10.3, since 📌 CdnIntegrationTest::testCss() fails on Drupal >=10.3 since #3432183 Needs review .

The 5.x branch now exists. So let's bump the requirements here.

The FullyValidatable validation constraint only became available in Drupal 10.3, see https://www.drupal.org/node/3404425 → .

So, 5.x should require 10.3, not 10.2.

To get this MR to pass tests, this issue must also address all deprecations. For example: PHPUnit has become more strict, 📌 Require `langcode: …` only for simple config that contains translatable values RTBC , and more.

The two remaining PHPStan errors will be fixed by 📌 Adopt Drupal core 10.3 config validation infrastructure Active 👍

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