- Issue created by @project update bot
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-188138These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
Successfully manually tested the patch on Drupal CMS RC incl. creating uuid reference fields via UI to terms, users and nodes.
Please commit and create a new release D11 compatible because some of my contrib and custom modules depending on this module.
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
In other words: The bot is right that there is no more needed than just fixing "core_version_requirement" compared to D10.
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
For testing via composer.
Install patch management:
composer require cweagans/composer-patches
For using D10 marked projects in D11:
composer require mglaman/composer-drupal-lenient
Add to "extra" section in main composer.json:
"drupal-lenient": { "allowed-list": [ "drupal/entity_reference_uuid" ] }, "patches": { "drupal/entity_reference_uuid": { "Automated Drupal 11 compatibility fixes for entity_reference_uuid, #3430230": "https://www.drupal.org/files/issues/2024-03-17/entity_reference_uuid.2.1.0.rector.patch" } },
To get the automated patch working, we need the dev version.
composer require 'drupal/entity_reference_uuid:2.0.x-dev@dev'
- Status changed to RTBC
13 days ago 2:50pm 16 April 2025 - 🇦🇲Armenia murz Yerevan, Armenia
@c-logemann, thank you for the workaround to still install the module on D11! Tested the module on Drupal 11.0 and 11.1 and it works well without any issues, so marking as RTBC, let's merge this short and easy fix?
Interesting, I came to this module following a request to have something like it in core: https://www.drupal.org/project/drupal/issues/2874548 ✨ Add a choice to use UUID in entity reference values instead of the entity's ID Needs work
A non profit wanted to use views data export to CSV with UUID then import thousands of nodes into Drupal 11 and reference them with UUID instead of entity Id for other content types... Hoping you can get this to D11 officially.