Every major version bump has that one relative who shows up, rearranges your furniture, and insists it's "for your own good." Drupal 12 is shaping up to be the rare exception — less demolition, more Marie Kondo. The scaffolding's mostly built; the core team is just deciding which boxes finally go to the curb.

The Second Window Is the Target

Drupal 12.0.0 has three possible release windows, and the community is now aiming for the second one: the week of August 10, 2026, contingent on clearing seven release-critical requirements — including PHPUnit 12 support, an Import Maps API that CKEditor 5 needs for its new install method, updated database fixtures for the upgrade path, and deprecating the old Toolbar module now that Navigation has gone stable.

Under the hood, the main branch already runs on Symfony 8, PHP 8.5 becomes the minimum runtime, Argon2id replaces the old password hashing default, and six legacy core modules are getting the boot. Gin is also on track to replace Claro as the default admin theme.

Why This Upgrade Won't Feel Like Drupal 7 to 8

The last time Drupal did a generational reset, half the ecosystem needed a full rebuild. This time, the scary stuff — Single-Directory Components, Workspaces, the Recipes API — already landed and stabilized during the 11.x cycle. Drupal 12 is less "new framework" and more "old framework, finally allowed to throw things away."

The catch nobody wants to hear: "evolutionary" still means auditing every contrib module and custom theme for what breaks when Toolbar disappears and Claro stops being default. The sites that skip that homework now are the ones filing panicked support tickets in December.

Drupal 12 isn't a cliff edge — it's a checklist. Better to run it in August than discover it in a support queue.

If your Drupal build is still leaning on modules or themes that Drupal 12 is about to sunset, let's map out the upgrade path before it maps itself onto your deadline — talk to WTK about a Drupal 12 readiness check.

Source: Drupal.org