Install
Works with Drupal: ^11.4 || ^12Using Composer to manage Drupal site dependencies
Alternative installation files
Release notes
https://git.drupalcode.org/project/civicrm_entity/-/work_items/3628599
https://git.drupalcode.org/project/civicrm_entity/-/merge_requests/53
Contacts no longer carry the undeclared $contact->groups (group IDs) and $contact->tags (tag names) properties that API3 loads used to leave on them. They were never fields, and requesting them joined the group, smart group cache and tag tables on every contact load. Code that read them should use the GroupContact and EntityTag APIs, or the civvicrm_group_contact and civicrm_entity_tag entity types.
auto and api4_native modes already didn't set them.
Small Backwards Compatibility Change
Check your custom code and Twig templates. Loaded civicrm_contact entities no longer carry groups and tags values. These were never entity fields, so they did not appear in Manage display or Views, but custom code could read them as plain properties:
$contact->groups
(comma-separated group IDs, including smart groups) and
$contact->tags
(comma-separated tag names), or in Twig, for example {{ elements['#civicrm_contact'].groups }}. They are now empty. If you used them, fetch the same values from the CiviCRM API instead:
civicrm_api3('Contact', 'getsingle', ['id' => $contact->id(), 'return' => ['group', 'tag']]) returns them as groups and tags.