ECA 3.1.11 and Project Browser 2.1.6 Address Drupal Workflow and Compatibility Issues

Released on 6 and 7 November 2026, Project Browser 2.1.6 and ECA 3.1.11 address compatibility testing and automation reliability in Drupal. Project Browser updates its test installer implementation for newer Drupal versions, while ECA fixes an event-subscription index that could become stale after direct configuration changes, potentially allowing disabled workflows to keep running.

The two stable maintenance releases also address a shared patch compatibility problem. Changes incorporated into Project Browser made patches carried by ECA unnecessary, and an ECA issue report documented Composer Patches errors when those patches were applied against the updated code. The updates are relevant to teams testing upcoming Drupal versions and maintaining automated workflows.

Project Browser 2.1.6 Updates Installer Compatibility for Drupal 11.5

Project Browser 2.1.6, released on 6 November 2026, focuses on compatibility with upcoming Drupal versions rather than new site-building functionality. The maintenance release fixes missing methods in its test module installer and addresses PHPStan static analysis issues associated with Drupal 11.5. It supports Drupal 11.2 and later Drupal 11 versions, as well as Drupal 12.

The release resolves two problems involving Drupal's evolving ModuleInstallerInterface. Project Browser's TestModuleInstaller lacked the getModulesToInstall() and getModulesToUninstall() methods required by newer core development branches. According to the first issue report, the missing installation method caused PHPStan bootstrap failures in ECA's continuous integration pipeline and other downstream testing environments. The second issue documented a similar failure involving the uninstall method while testing against Drupal core's main development branch.

The update also includes PHPStan fixes for Drupal 11.5 compatibility. Project Browser maintainer phenaproxima confirmed in the issue discussion that the changes addressed internal testing problems. These fixes reduce compatibility-related failures in development pipelines but do not represent a reported failure of Project Browser's user-facing module discovery interface.

ECA 3.1.11 Repairs Event Subscriptions and Removes Obsolete Patches

ECA 3.1.11, released on 7 November 2026, fixes how the Event - Condition - Action (ECA) module maintains event subscriptions after direct configuration changes. The underlying issue explains that changes made through drush config:set or Drupal's editable configuration API could bypass the entity save process that normally rebuilt ECA's subscribed-event index. Consequently, disabled models could continue executing, while models enabled through the same mechanism might remain inactive.

The issue report, published by ECA maintainer Jürgen Haas, describes eight production sites running ECA 2.1.24 where a model disabled through direct configuration changes continued sending notifications for three months. The report also documents reproduction of the underlying behaviour with Drupal 11.4.11, ECA 3.1.10 and Drush 13.8.0. The fix rebuilds event subscriptions following relevant configuration changes, prevents disabled models from executing even if the index is stale, adds recovery during cache rebuilds and includes a post-update repair for existing installations. ECA 3.1.11 supports Drupal 11.3 and later Drupal 11 versions, as well as Drupal 12.

The release also removes two Project Browser patches that had become redundant following version 2.1.6. An issue report documented Composer Patches errors when ECA 3.1.10 attempted to apply changes already incorporated upstream. Separately, ECA 3.1.11 fixes Render: Twig validation by parsing templates instead of rendering them during validation. This addresses a reported problem in which valid Twig expressions involving division by a variable were rejected, blocking Drupal 10-to-11 migration testing for the reporting contributor.