Public signals can indicate an end-of-life Drupal release without showing whether a site receives commercial security coverage. That distinction shapes how the study's version findings should be read.
...more
A Drupal field automator can now delegate work to an AI agent that searches, calls tools and completes multiple steps before returning the value to be stored.
...more
Sites that rely on these extensions need to identify the dependency before crossing the Drupal 12 upgrade boundary, rather than after core stops supplying it.
...more
A Drupal 10-to-11 module upgrade can fail when Site Verification's update sequence meets unreconstructed routing data. The original fix has already been followed by Site Verification 3.0.2.
...more
Release state changes the response: some Drupal changes are ready to use, some warrant a targeted update, and others belong in testing rather than production.
...more
Core contributors and continuous integration maintainers need to account for the new JavaScript development baseline without treating it as a Drupal 11 or production hosting requirement.
...more
Frontend teams no longer have to patch Druxt to expose additional Drupal configuration resources, but administrators still need to treat each enabled resource as broadly readable to permitted clients.
...more
A new Drupal 11 module gives developers a way to keep domain behaviour behind interfaces instead of spreading field-specific logic across calling code.
...more
Teams with long-running FlowDrop installations now get a clearer view of accumulated execution history, but version 2.6 stops at reporting rather than automatic deletion.
...more