By Greg Nowak. Updated 8 November 2026.
If your Drupal maintenance plan still depends on the first-generation Automatic Updates API, it needs attention. The immediate task is to establish how your next security update will reach production, who will handle it, and how you will recover if something breaks.
The shutdown affects the infrastructure used by Automatic Updates 7.x-1.x and 8.x-1.x. It does not mean every Drupal update mechanism has stopped working. The Drupal Association’s shutdown notice now marks discontinuation as immediate, superseding its earlier timetable. Legacy release-content hash files expired on 12 May 2026 and may be removed without notice.
Start with ownership and an inventory
For a business owner, the useful question is: “Can our team deliver a security update without improvising?” For an agency, that includes knowing where its responsibility ends and the hosting provider’s begins.
Record each site’s Drupal version, Automatic Updates branch, PHP and Composer versions, hosting restrictions, repository, deployment process, and backup location. Name the person who receives security notices, the person who performs updates, and whoever can approve an urgent release. Check scheduled jobs and old maintenance instructions too; a working website does not prove its updater still works.
Choose an update route that fits your hosting
My recommendation is to follow the way code already reaches production. If your team deploys reviewed changes through Git and CI, keep updates within that process. Browser updates make more sense where the hosting environment deliberately supports Drupal changing its own application files.
| Your setup | Practical route | Check before proceeding |
|---|---|---|
| Drupal 7 or 8 with Automatic Updates 1.x | Plan migration and confirm an interim maintenance arrangement | Who supplies security fixes while migration is underway? |
| Supported Drupal core on compatible, writable hosting | Evaluate the matching Automatic Updates release | Can staging complete an update and a recovery rehearsal? |
| Git and CI deployment | Resolve dependencies in development or CI, test, then deploy | Are dependency changes recorded in the repository? |
| Immutable containers or release artifacts | Build and promote a replacement artifact | Can the previous release be restored with compatible data? |
Separate module compatibility from core security support
As of this update, the Automatic Updates project lists 4.1.0 for Drupal ^11.2 and 3.1.7 for ^10.1 || ^11. Those constraints describe package compatibility; they do not make every matching core release a sensible maintenance target.
The Drupal 11.2 release notes require Automatic Updates 4.0.0 or later when crossing that core upgrade boundary. They also state that Drupal 11.2.x security support ended in June 2026. In November, “compatible with 11.2” is therefore not a recommendation to remain on 11.2.
Choose a currently supported core release, then resolve the appropriate module version against the whole project. Avoid copying a generic installation command from introductory documentation without checking the release-specific requirements.
Check Composer before changing dependencies
Ask the technical owner to run these checks from the project root in a development checkout:
php --version
composer --version
composer validate
composer show drupal/core-recommended
composer show drupal/automatic_updates
composer audit --lockedIf the project does not use drupal/core-recommended, inspect drupal/core instead. An absent Automatic Updates package means you should investigate how updates are actually performed.
According to the Composer command documentation, validate checks the project definition and agreement with an existing lock file. audit --locked checks the locked package set rather than whatever happens to be installed. Review findings alongside Drupal advisories.
Resolve changes outside production, review the dependency diff, and commit both composer.json and composer.lock when changed. Deploy from the reviewed lock file. Update Composer through the host, image, or CI toolchain that manages it.
Check Package Manager’s actual requirements
Automatic Updates 4.x uses core’s experimental Package Manager. It stages Composer changes in a temporary copy before synchronising them back. The current Package Manager documentation requires writable application code, including vendor; Composer satisfying ^2.7; PHP permission to run Composer; enabled proc_open(); valid Composer files; secure downloads; and rsync.
It also requires configured PHP-TUF protection for Drupal’s Composer repository. Include private repositories and Composer plugins in the rehearsal. If cweagans/composer-patches is installed, it must be a root dependency.
Where Composer discovery fails, set its executable path in settings.php:
$config['package_manager.settings']['executables']['composer'] = '/full/path/to/composer.phar';That fixes discovery only. It does not grant permissions or make an incompatible hosting platform suitable.
Give automation an owner and a recovery plan
The 3.x branch documents this console entry point:
php /path/to/module/automatic_updates/auto-updateTreat it as branch-specific guidance. Before scheduling anything, verify the installed version’s behaviour, execution account, logs, and failure alerts. Assisted updates and unattended updates require different operating decisions.
Make the rehearsal concrete:
- Prepare recovery: verify usable database and file backups, retain the previous code release, and agree how new orders or submissions will be handled during restoration.
- Run the release: apply dependency changes, required database updates, and the normal deployment steps in staging.
- Test business journeys: check login, enquiries, checkout where relevant, scheduled tasks, and important integrations.
- Test failure handling: confirm someone receives an alert and can follow the recovery instructions.
Write down the commands, approver, checks, recovery steps, and escalation contact. That gives the next person something dependable to follow during an urgent release.
If your Drupal estate spans older versions, several suppliers, or custom Composer behaviour, talk to Greg about reviewing the update path. A focused review can identify the blockers and define a practical maintenance runbook your team can use.
Related on GrN.dk
- One Webform Release, Twenty Advisories: Audit Every Drupal Site
- WordPress Plugin Updates: What the Six-Hour Cooldown Can’t Check
- Drupal 7 HTTPRL Network Errors: Fix the Warning, Check the Work
Need help with this kind of work?
Review your Drupal update path with Greg Get in touch with Greg.