Project Update Bot Starts Drupal 12 Readiness Patches for Contrib

Staff Reporter

Promotional graphic titled "Project Update Bot Targets Drupal 12 Readiness." The text highlights that automated patches now address deprecated API use with Drupal Rector rule coverage exceeding 80%. The background shows blurred data charts alongside a blue Drupal mascot icon.

Contributed Drupal projects are receiving Drupal 12 readiness patches from a refreshed Project Update Bot, according to an announcement by Björn Brala on 9 June 2026. The bot scans projects and opens issues with patches intended to fix deprecated API uses before Drupal 12.0.0, which is scheduled for the week of 7 December 2026 UTC.

The update addresses one of the larger maintenance tasks in a Drupal major-version cycle. Thousands of contributed modules and themes may need deprecated API usage updated before they are ready for Drupal 12. Automated scanning and patch generation give maintainers a starting point for reviewing compatibility work rather than replacing maintainer review.

Björn said the Drupal 12 cycle expanded Drupal Rector rule coverage to more than 80% of deprecated API uses introduced for the release. The workflow uses Upgrade Status for analysis, Drupal Rector for automated fixes, and Project Analysis to connect the process.

The announcement credits part of the expanded rule coverage to AI-generated Rector rules based on Dries Buytaert’s drupal-digests. It also says the refreshed bot now resolves submodule dependencies during analysis. Earlier cycles scanned submodules without their dependencies, which the announcement says caused failed scans and false errors.

A Project Update Bot issue for A11Y Project Checklist shows how the process appears in practice. The issue was created on 9 June 2026 at 14:31 UTC and updated on 15 June 2026 at 10:18 UTC, with a Drupal 12 compatibility patch, an interdiff, and an associated merge request. The issue summary tells maintainers that the generated changes have not been manually or automatically tested and should be reviewed before use.

Patches may arrive as GitLab issues or Drupal.org issues, depending on the project. Each issue opened by the bot explains how maintainers can apply the patch, pause further bot updates, or close the issue.

Questions and feedback are being directed to the #d12readiness channel on Drupal Slack. The announcement also asks maintainers to report incorrect patches in the Drupal Rector or Project Analysis issue queues so the underlying rule can be corrected for other projects.

Reference: The Project Update Bot is refreshed for Drupal 12 readiness with over 80% automated coverage for deprecated APIs by Björn Brala (bbrala) (9 June 2026)

Drupal 12

Contributed Modules

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.