Skip to main content

Pantheon release notes

Your destination for staying informed about our latest innovations and product updates.
Subscribe to RSS feed
May 12, 2026

Today Pantheon announces a removal schedule for Solr 3 on February 9, 2027 and Solr 8 on July 11, 2027. Solr 9 will reach General Availability on June 30, 2026 ahead of these removals.

After a Solr version is removed from the platform, sites using that version will no longer be able to index content or return search results. Views, blocks, or other components that rely on Solr-powered search indexes may return no results or throw errors.

Solr 9 - General Availability: June 30, 2026

Solr 9 has been available as a Beta for Drupal 10 and 11 sites through search_api_pantheon version 8.5.0-beta1. Solr 9 Beta for Drupal 7 is now available as of May 12, 2026.

General Availability for Solr 9 is targeted for June 30, 2026.

Solr 3 - Removal: February 9, 2027

Solr 3 will be removed from the Pantheon platform on February 9, 2027. Solr 3 is a legacy search version that no longer receives security updates.

Previous milestones:

Drupal 7 sites still using Solr 3 must migrate to Solr 9 before this date. See the Solr for Drupal 7 guide for upgrade steps. WordPress sites should migrate to Elasticsearch or another supported search solution before January 11, 2027.

Solr 8 - Removal: July 11, 2027

Solr 8 (8.11.4) will be removed from the platform on July 11, 2027. Solr 9 supersedes Solr 8 with improved security defaults and other enhancements. Drupal 10 and 11 sites currently running Solr 8 should migrate to Solr 9 before this date. Upgrade instructions are available in the Solr 9 Beta announcement.

Action required

  • Drupal:

    • Solr 3 sites: Migrate to Solr 9 before February 9, 2027.
    • Solr 8 sites: Migrate to Solr 9 before July 11, 2027.

    For guidance on upgrading, see Drupal Solr.

  • WordPress:

May 12, 2026

Pantheon Search with Apache Solr 9.10.0 support for Drupal 7 is available as a beta release for testing on Multidev environments. Do not deploy Solr 9 changes to Dev, Test, or Live. At GA, the updated module will be available as a one-click upstream update.

This extends the Solr 9 beta support previously announced for Drupal 10 and 11.

For setup instructions, required module versions, upgrading from Solr 3, and custom config details, see Using Solr on Drupal 7.

What about Solr 3?

Solr 3 remains supported for Drupal 7 sites during the Beta period. Solr 3 will be removed on February 9, 2027. Sites using Solr 3 should plan to upgrade to Solr 9.

Solr 3 is no longer supported for Drupal 9.4+ as of December 9, 2025. Those sites must use Solr 8 or above.

May 12, 2026

PHP versions 8.2.31, 8.3.31, 8.4.21, and 8.5.6 are now available on the platform. These updates include important security fixes, along with bug fixes and enhancements that improve performance and stability. Updates will be applied automatically over the next few days, so no manual action is required.

May 11, 2026

PHP 7.2, 7.3, and 8.0 have reached End of Sale on the Pantheon platform. New sites can no longer be created using these PHP versions.

This was previously announced in the PHP version removal schedule published March 11, 2026.

These versions, along with PHP 5.6, 7.0, and 7.1, are scheduled for removal on September 30, 2026. Sites still running a removed PHP version will be automatically upgraded to the oldest available PHP version at the time of removal.

Action required

If your site is running PHP 7.2, 7.3, or 8.0, upgrade to a recommended PHP version before September 30, 2026 to avoid disruption. Pantheon recommends PHP 8.3 or 8.4 for all production sites.

For guidance on upgrading, refer to Upgrade PHP Versions.

Sites created with custom upstreams that specify an end-of-sale PHP version may also experience unexpected behavior upon site creation.

May 4, 2026

PHP versions 8.4.20 and 8.5.5 are now available on the platform. These updates include bug fixes and enhancements that improve performance and stability. Updates will be applied automatically over the next few days, so no manual action is required.

April 30, 2026

Terminus 4.2.1 is now available. This patch release fixes a pagination bug affecting org:site:list and a WordPress-specific issue.

Key improvements in this release

  • Fix incomplete site listings: org:site:list could return truncated results when the API returned short pages, affecting organizations with sites in supporting workspaces (#2829)
  • WordPress fix: Only include wp_replace_siteurl if the site is WordPress (#2825)

How to upgrade to Terminus 4.2.1

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

For more information about this release, visit the GitHub release page.

If you have questions or concerns around Terminus, please use the Terminus issue queue.

April 30, 2026

Sites with Multizone Failover enabled are now eligible for the Global CDN (GCDN) Beta. Previously, Multizone Failover sites were excluded from the Beta — that restriction has been removed.

What's changed

  • Multizone Failover is no longer listed as an excluded configuration for the GCDN Beta.
  • Eligible Multizone Failover sites will see the GCDN Beta banner in the Pantheon site dashboard.

No action is required. If you operate a Multizone Failover site, simply look for the GCDN Beta banner on your site dashboard and follow the guided steps when you're ready to migrate.

More information

For full details on the GCDN Beta, see the GCDN Beta documentation.

April 29, 2026

As previously announced, Tika 1.18 and 1.21 have been removed from the Pantheon platform. All sites now run Tika 3 regardless of the tika_version setting in pantheon.yml.

Action Required

  • If you have not already done so, remove tika_version: 1 from your pantheon.yml before May 12, 2026.
    • Any tika_version: 1 entries will be ignored until May 12, 2026, at which point they will be rejected and prevent deployments.
  • Update the used Tika 1.x path to Tika 3, for details see related documentation.
    • Existing Tika 1.x file paths will continue to symlink to the new Tika 3 location for the time being, but these symlinks will be removed at a later date.