Cloudflare Purge 3.1.4 Adds Drupal 12 Support and Fixes API Error Handling

Released on 6 October 2026, Cloudflare Purge 3.1.4 adds Drupal 12 compatibility and fixes a fatal error that could occur when the Cloudflare API returned an unsuccessful cache-purge response. The contributed module continues to support Drupal 10 and 11 and requires PHP 8.1 or later.

The problem affected the error path rather than successful purge requests. Drupal 12 ships with Guzzle 8, where methods used by the module's earlier response handling were no longer available. A bad token, rate limit or Cloudflare 5xx response could therefore end in an undefined-method fatal error instead of being returned as a failed purge result.

Error Handling Now Works Across Guzzle 7 and 8

Version 3.1.4 changes how unsuccessful responses are resolved so the module works with Guzzle 7 on Drupal 10 and 11 and Guzzle 8 on Drupal 12. The project documentation specifically identifies bad credentials, rate limits and server-side Cloudflare errors among the cases affected by the previous behaviour.

The release also completes compatibility work needed for Drupal 12, including fixes for deprecations and service discovery. The module's current requirements declare Drupal ^10 || ^11 || ^12 and PHP 8.1 or later.

Earlier 3.1 Changes Remain Part of the Upgrade Context

The current 3.1 branch also includes automatic batching for large purge requests, operation-wide handling of authentication and rate-limit failures, and protection against oversized Cache-Tag headers. These are broader 3.1-series capabilities rather than changes introduced specifically by 3.1.4.

Large lists of URLs, cache tags, prefixes or hostnames are split into API-sized batches of up to 100 items. The module can continue past an individual failed batch but stops an operation when it encounters a rate limit or authentication failure that applies to the request as a whole.

The cache-tag handling also limits headers that could otherwise grow beyond common web-server or CDN limits on tag-heavy pages. The project documentation says purge calls and emitted headers now use the same filtered tag set.

No Database Update Is Required

According to the project documentation, Cloudflare Purge 3.1.4 does not require an update hook. Maintainers should update the module and run drush cr so Drupal rebuilds its caches.

Cloudflare Purge provides an independent Drupal integration for Cloudflare cache invalidation through the administrative interface and Drush. It supports full-zone purges as well as purging by URL, cache tag, prefix and hostname, with optional automatic cache-tag invalidation and queue processing for larger workloads.

The project page lists version 3.1.4 as the current stable release, covered by Drupal's security advisory policy. That coverage does not make this a security release; the October update is a compatibility and bug-fix release focused primarily on Drupal 12 and failed API-response handling.