Did you know that Drupal 12 is expected as early as mid-2026? That is in 8 months! Drupal 11.2 already defined most deprecated APIs and disruptive deprecations are now deferred to Drupal 13. So it was time to look at where the contributed ecosystem stands and kick off the creation of automations (for example rector rules) to help the ecosystem along.
First SWIS' CTO Björn Brala updated the Project Analysis scripts to be able to run on Drupal 11 checking for Drupal 12 compatibility. These rely on Upgrade Status, which provide your personal checklist to keep your site as compatible as possible. That of course can already be used to check your Drupal 12 readiness!
Since we had the data, the next step was to visualize it! I maintain the Deprecation Status dashboard, but the Acquia Developer Portal was in the middle of upgrades. So I worked with Josh Waihi at Acquia to include support for a Next.JS frontend for the dashboard. So the new home for Drupal 12 ecosystem readiness data is on docs.acquia.com, enjoy the new data and much faster responsive frontend!
So far our data shows that almost 70% of projects only need an info.yml/composer.json file change and almost 80% of all errors are info.yml/composer.json related. Even if there may be some missing areas in our checking at this early stage, that is very promising!
There may be little bugs here and there with the frontend, let me know in #d12readiness on Drupal Slack!