Support Drupal 11

The drupal11 MR fixes all the issues noted by the Upgrade Status module. However, I think we still need 📌 Automated Drupal 10 compatibility fixes RTBC , and even then, the unit tests still need to be fixed.

Also, it would be a lot easier to test this if we had 📌 Add GitLab CI template Needs review .

When 🐛 Compatibility with Drupal 10.2: Encrypting fields not possible in the UI RTBC is in, the unit tests will pass, so I think this is ready for review.

The Drupal 11 fixes from Updatebot included 📌 Automated Drupal 10 compatibility fixes RTBC , so that issue can be closed if this is committed first.

@ptmkenny with PHPStan and Drupal 11 we need to add

phpstan (next major):
  allow_failure: true

to .gitlab-ci.yml because we don't want to fail on D10 and it is great to know about the D11 fails / changes but we don't want to act on them yet - because we still support Drupal 10.

@alexpott Actually, I think we can fix phpstan for Drupal 11 without breaking anything for D10. There's this change record → , but since we are requiring 10.2, we can go ahead and add the new parameter to both 10 + 11.

When I run phpunit locally I'm also seeing this notice (adding a note now to take a look at this again before finalizing the MR):

Remaining self deprecation notices (2)

  2x: The definition for the 'encrypt.profile.encryption_profile_2.encryption_method_configuration' sequence declares the type of its items in a way that is deprecated in drupal:8.0.0 and is removed from drupal:11.0.0. See https://www.drupal.org/node/2442603
    2x in EntityHooksTest::testStatusReport from Drupal\Tests\field_encrypt\Functional

With regard to #10, this seems to be a mistake in the deprecation checker. It doesn't like this line:

'encryption_method_configuration' => ['mode' => 'CFB'],

but using a nested array to generate the value seems fine, and the tests are all passing on Drupal 11, so I think this is safe to ignore.

Thanks @ptmkenny this looks great.

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