Drupal Release Digest: AI Fixes, Stripe Payment Methods and Microsite Aliases

Three Drupal contributed projects published releases on 16 September 2026 covering AI workflows, Commerce payments and LocalGov Microsites deployment. Drupal AI released versions 1.4.9 and 1.3.14, Commerce Stripe released 2.2.2, and LocalGov Microsites Domain Alias published its first alpha. The releases are independent project updates rather than parts of a coordinated Drupal release.

Drupal AI versions 1.4.9 and 1.3.14 are bug-fix releases for the maintained 1.4.x and 1.3.x branches. Their release notes include fixes affecting AI Automators, validation, tool-call handling and compatibility work, while 1.4.9 also includes an access-related correction for AI API Explorer. Both releases support Drupal ^10.5 || ^11.2. The Symfony 8 compatibility work is relevant to forward-compatibility testing, but the supported core constraint does not establish Drupal 12 compatibility. These releases are maintenance updates rather than security advisories and follow earlier coverage by The DropTimes of Drupal AI 1.4.7 and 1.3.12.

Commerce Stripe 2.2.2 adds basic support for a broader range of Stripe payment methods through the Payment Element while retaining strongly typed handling for commonly used methods. The release also includes bug fixes and additional Payment Element test coverage. Which payment methods are actually offered to a customer still depends on the Stripe account and the conditions Stripe applies to a transaction, including factors such as currency and location.

LocalGov Microsites Domain Alias 1.0.0-alpha1 creates predictable Domain Alias records for microsites across configured environments such as local development, staging and production. This lets teams give a microsite a usable environment-specific hostname before its public production domain is pointed at the platform and reduces manual domain changes after database copies between environments.

The LocalGov module requires Drupal 11.2 or later, Domain with Domain Alias, Group 3 and Group Context Domain, and integrates with LocalGov Microsites Group. It creates the alias records inside Drupal but does not configure the surrounding infrastructure: teams still need DNS, a web server or hosting platform that accepts the generated hostnames, appropriate TLS certificates and compatible trusted_host_patterns where those are configured. The project remains an alpha release and is not covered by Drupal's security advisory policy. It was developed for LocalGov Drupal microsite platforms.