Skip to content
← Back to Blog

Your Drupal Maintenance Contract Was Written for a Slower Schedule

Two upgrades a year, each with about two months to finish. Where government contracts miss the window, what to put in the next RFP, and what reports should show.

Plenty of cities, counties, transit agencies, utilities and state agencies run Drupal. Many of those sites are maintained under a contract written around the old rhythm, with one minor upgrade a year and a major upgrade when a version goes end of life.

That rhythm just changed. Starting in 2027, each minor version of Drupal core gets eight months of security support instead of twelve. Two upgrades a year are now the minimum, each with roughly a two-month window. A contract that needs a new work order, a quote and an approval for every upgrade can miss that window without anyone doing anything wrong.

Where this comes from. The Drupal Security Team's announcement of November 2, 2026 (PSA-2026-11-02) and Drupal's core release schedule, read directly, plus what we see in government website RFPs.

The Dates a Government Site Has to Hit

  • On Drupal 10.6 or 11.3. Security support ends the week of December 7, 2026. Drupal 10 reaches end of life on December 9.
  • On Drupal 11.4. Supported until April 21, 2027.
  • From 2027 on. New minor versions every June and December. Each previous version stays covered for about two months after the next one ships.

Where Government Contracts Trip

When a government maintenance contract misses this schedule, the cause is usually in the contract, not the software. Three patterns to look for:

  • Every upgrade is a change order. If each upgrade needs its own quote, purchase order and council or board approval, the two-month window can close while the paperwork is still moving.
  • Security updates are covered. Upgrades are not. Many maintenance contracts promise to apply security updates but say nothing about keeping core on a supported minor version. Those are different jobs.
  • The renewal lands on the release. A one-year contract signed with a December renewal date can put the vendor transition right on top of the December release.

What to Put in the Next RFP or Renewal

Four lines in an RFP or a renewal close most of the gap:

  • Stay supported. The site will run on a Drupal core version that has security support at all times.
  • Set a clock for security releases. Drupal core and contributed module security releases rated critical are applied within a stated number of days of publication.
  • Include the upgrades. Minor upgrades are part of the monthly scope, not separate projects requiring new approval.
  • Prove it. Upgrades are tested on a non-production copy of the site, and the vendor reports the core version and any outstanding advisories every month.

What Monthly Reporting Should Show

A procurement office cannot judge an upgrade it cannot see. A one-page monthly report from the vendor should answer four questions:

  • What version are we on? The exact Drupal core version running on the live site.
  • When does it lose support? The date security support ends for that version, from Drupal's published schedule.
  • What is outstanding? Any core or module security advisories that apply to the site and have not been applied yet, with the reason.
  • What is next? The date of the next minor upgrade, and whether it has been tested.

If a vendor cannot produce that page, the agency does not know whether its site is supported. That is worth finding out before a council member or an auditor asks.

The Accessibility Overlap

Large cities, counties and state agencies face the ADA Title II web accessibility date of April 26, 2027, five days after Drupal 11.4 loses support. Smaller governments and special districts are on April 26, 2028. A pending lawsuit asks a federal court to undo that one-year extension, which would bring the earlier dates back. The same team usually does both jobs, so plan them together: accessibility fixes made on a version that is about to lose support have to be carried through the upgrade anyway.

Keep Your Drupal Site on a Supported Version

Our partnership plans give you a team that tracks Drupal core and module security releases, applies the updates, and schedules the two minor upgrades a year so your site does not run on an unsupported version. Every plan is a set number of hours each month, so security updates, upgrades and improvements come out of the same predictable budget.

See our partnership plans →

Ask about your Drupal site →

83 Creative

We're a web development studio that works exclusively with trade associations, professional societies, and membership organizations.

← Previous Article CISA Says the WordPress Update Flaw Is Being Exploited. Block One Folder Before You Update.