Drupal's core release schedule got a concrete update on June 4, 2026, and if you're running any Drupal 10 or 11 site in production, the dates now on the calendar are worth putting into your roadmap. Paired with a freshly retooled Project Update Bot that targets Drupal 12 compatibility, there's more upgrade tooling available right now than at any previous major-version transition — but the window to act at your own pace is narrowing.
What the schedule confirms
The updated Drupal.org core release schedule pins three significant milestones for the second half of 2026:
- Drupal 11.4.0 — targeted for the week of 22 June 2026. This is a minor release on the current stable branch, but it's the last minor before the ecosystem's attention fully shifts toward 12.
- Drupal 12.0.0 — scheduled for later in 2026 (the exact week is still tracked on the official schedule page but sits in Q3/Q4 planning territory). This is the next major version, meaning it will drop support for some deprecated APIs and raise the PHP floor.
- Drupal 11.5.0 — also on the schedule alongside 12.0.0, confirming that Drupal 11 will receive at least one more minor after 12 ships, giving teams a longer tail before 11.x reaches end-of-life.
Separately, the Project Update Bot — the automated tooling that scans contributed modules and themes and files compatibility patches — has been significantly refreshed ahead of the Drupal 12 release cycle. The bot now covers automated Rector rule fixes for more than 80% of deprecated API uses introduced in the 12.x development cycle. That's a meaningful jump from previous cycles, where the bot's coverage was spottier and more manual remediation was expected.
For context: the Project Update Bot doesn't just flag problems. It actively files merge requests against contributed module repositories with proposed code changes, which dramatically accelerates the contrib ecosystem's readiness for a major release. In the Drupal 9-to-10 transition, the bot was widely credited with shrinking the "contrib not ready" window from months to weeks on many popular modules.
Our take
The 80% Rector coverage number is genuinely good news — but don't let it lull you into passivity. The 20% of deprecated API uses that aren't covered by automated rules tend to be the harder ones: custom modules with unconventional patterns, contrib modules that haven't seen a commit in 18 months, or integrations that depend on APIs that fundamentally changed rather than just got renamed. Those are exactly the cases where automated tooling runs out of rope and an engineer needs to make judgment calls.
Drupal 11.5.0 being on the schedule matters more than people are crediting. The fact that Drupal 11 gets another minor release after 12.0.0 ships gives any site still on 11.x a meaningful buffer. It means you're not immediately on a deprecated branch the day 12.0.0 goes out. For clients with complex builds — heavy contrib dependencies, custom entity types, legacy integrations — this buffer is real planning leverage. We'd use it deliberately, not as permission to delay indefinitely.
The D10 situation is more urgent than D11. If any of your sites are still on Drupal 10, the timeline tightens faster. Drupal 10's end-of-life is already confirmed for around the time 12.0.0 ships. Skipping 11 to go straight from 10 to 12 is technically possible but practically painful — the deprecation surface between 10 and 12 is larger than between 11 and 12. The upgrade path from 10 → 11 → 12 is cleaner and the tooling is better.
The Project Update Bot's refreshed coverage changes our contrib audit approach. On previous major version transitions, our standard practice was a full manual audit of every contrib module before advising a client on upgrade readiness. The bot's Rector coverage now means we can lean on automated analysis as the first pass and focus human review time on the flagged gaps. For a typical mid-size Drupal site running 30–50 contributed modules, this can realistically cut the initial audit time from a day to a few hours.
Don't treat "80% automated" as "80% done." We've seen this mistake before. A site can pass automated Rector checks and still have runtime failures because of behavioral changes in APIs that weren't deprecated in a way Rector can catch, or because of theme-layer changes that are hard to test statically. Full upgrade validation still requires a staging environment, a regression test suite, and hands-on QA.
Practical recommendations by site type
If you're on Drupal 10:
Start your upgrade to Drupal 11 now. Don't wait for 12. Run drush rector against your custom modules today to see your actual deprecation surface. This is the path of least resistance to long-term support.
If you're on Drupal 11.3 or earlier: Upgrade to 11.4 when it ships the week of June 22. It's a minor release — your risk is low and it keeps you current. Then use the 11.4 → 11.5 window to run the Project Update Bot's Rector analysis against your custom code and contrib dependencies, and build your 12.0 upgrade plan.
If you're on Drupal 11.x and your contrib stack is modern: Run the Drupal 12 compatibility check on your modules now via Drupal.org's project pages or the Update module. The bot has already filed patches for many popular modules — you may find that your dependency list is already largely 12-compatible.
Pre-upgrade checklist for any major version jump:
- Audit custom modules with
drush rector --dry-run(Rector 2.x for D12 targets) - Check all contrib modules for a "12.x compatible" release or an open bot-filed merge request
- Spin up a staging environment on the target PHP version (D12 raises the minimum floor — confirm with the official requirements)
- Run your full test suite on staging — if you don't have one, a Cypress or Playwright smoke suite covering critical paths is the minimum
- Diff content output on representative nodes before and after — render changes in major versions can quietly alter markup in ways that break styled components
Originally referenced: Drupal Core Schedule Confirms 2026 Release and Support Timeline on The Drop Times. Project Update Bot coverage details drawn from Project Update Bot Adds Drupal 12 Readiness Coverage, also on The Drop Times.
If you're running Drupal 10 or 11 and want a realistic assessment of what a Drupal 12 upgrade will actually cost — including a contrib audit, custom module Rector pass, and staging validation plan — get in touch.
Originally published by The Drop Times. Read the full announcement here.
