Automated Drupal 11 compatibility fixes for prlp

All green 🎉

Having looked at the code code changes for this issue and the 2.0.x branch, it is still quite compatible with Drupal 10.3. I can see it discussed in passing in this issue, but there does not seem to be a reason for dropping the older versions, not even D10 which is still actively supported core.

Could 10.3 be added to the supported cores on the 2.0.x branch? ie core_version_requirement: ^10.3 || ^11

This would allow for an easier upgrade between Drupal 10 and 11, as all of the modules can be updated to be compatible with D11 core, before the final push to switching over the core. At present, it has to be updated at the same time as core, tying the two together.

Also, the drupal/core requirement should be removed from the composer.json file. This is automatically generated from the contents of the info.yml core_version_requirement, making it a double up and possible future conflict if one of them is accidentally not updated.

@elc I believe you are correct.

Are you able to create a patch / PR which includes those changes?

Updating target version. Tests pass for all target cores. Setting to NR as this MR amends the D11 fixes.

Fixed in 2.0.1 release.

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