Project Update Bot Adds Drupal 12 Readiness Coverage

Maintainers preparing contributed projects for Drupal 12 now have expanded automation support from the refreshed Project Update Bot. In a Drupal.org core blog post published on 9 June 2026, Björn Brala said the bot now targets Drupal 12 readiness by scanning contributed projects and opening issues with patches for deprecated API usage.

The update matters because thousands of contributed modules and themes are expected to need changes for Drupal 12 compatibility. According to the post, the bot’s Rector rules now cover more than 80% of deprecated API uses introduced for the Drupal 12 cycle. That does not make projects automatically compatible, but it can reduce the manual work maintainers face when reviewing deprecated API changes.

The workflow combines several Drupal tools. Gábor Hojtsy’s Upgrade Status module handles analysis, the Drupal Rector module generates automated fixes, and the Project Analysis module connects the scanning and patch workflow. The post also credits SWIS for maintaining much of the Drupal Rector work.

The refreshed bot also improves submodule dependency handling. Earlier cycles scanned submodules without fully resolving their dependencies, which could lead to failed scans and false errors. The updated analysis now resolves those dependencies, which Drupal.org says should produce cleaner and more accurate results.

Patch issues may appear on Drupal.org or GitLab, depending on the project repository. Each issue explains how maintainers can apply the patch, pause the bot, or close the issue. Brala also directed maintainers to the #d12readiness channel on Drupal Slack and asked contributors to report incorrect patches through the Drupal Rector or Project Analysis issue queues so rule fixes can benefit other projects.