Pantheon release notes

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:

• Solr 3 support for Drupal 9.4+ ended December 9, 2025
• WordPress Solr support ends January 11, 2027

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:

  • Migrate to Elasticsearch before January 11, 2027.

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.

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.

As noted in our June 2025 release note, Drush 5 and 7 are no longer available on Pantheon, and pantheon.yml files retaining these retired values would eventually cause a git push to be rejected. That enforcement is now in effect.

Pantheon now rejects git push when drush_version is set to 5 or 7 in pantheon.yml. The supported values are 8, 9, and 10.

Validation runs whenever pantheon.yml changes are detected on push, including reverts. Sites with drush_version: 5 or 7 already committed are unaffected until the file is modified. A git revert or git reset that touches pantheon.yml will also trigger validation and be rejected if the retired values are present.

Action required

Customers with sites configured for Drush 5 or 7 should upgrade the Drush version in pantheon.yml to at least Drush 8:

Sites created with custom upstreams using these versions may also encounter errors on site creation or upstream updates if drush_version is still set to 5 or 7.

Starting today, all Test and Live environments that have not yet been upgraded to PHP Runtime Generation 2 will be auto-upgraded over the course of this week. Opting out is no longer available.

After this week, PHP Runtime Generation 1 will no longer be available on the platform.

Action Required

If you experience any issues following the upgrade, please review the Known Changes and Requirements and contact support for assistance.

Starting today, all Dev and Multidev environments that have not yet been upgraded to PHP Runtime Generation 2 will be auto-upgraded over the course of this week. Opting out is no longer available.

What's next?

• April 13, 2026: Auto-upgrades will begin for Test and Live environments

We strongly recommend using this week to verify your site on Dev and Multidev before Test and Live environments are upgraded.

Action Required

If you have not already reviewed your site's compatibility with Generation 2, please check the Known Changes and Requirements and address any issues in your Dev or Multidev environments this week.

Tika config support for disabling OCR

Tika 3 enables OCR (Optical Character Recognition) via Tesseract by default, which can significantly increase processing times for PDFs and image-based documents. A bundled tika-config.xml is now available on all Pantheon environments to disable OCR:

Pass it to Tika using the --config flag:

See External Libraries: Apache Tika for details.

Search API Attachments module update for Drupal

Drupal sites using the Search API Attachments module can now disable OCR directly from the admin UI. Version 10.0.8 adds a Path to Tika configuration file field at /admin/config/search/search_api_attachments. Set it to /opt/pantheon/tika/tika-config.xml

Tika 1.x no longer available starting April 28, 2026

Tika 1.18 and 1.21 are being removed from the platform:

• April 28, 2026 — tika_version: 1 in pantheon.yml will be ignored. Sites will automatically use Tika 3.
• May 12, 2026 — tika_version: 1 in pantheon.yml will be rejected.

Following a successful Alpha phase, the next-generation Global CDN (GCDN) is now entering Beta. The new GCDN introduces bot protection by default — meaning sites that migrate will automatically benefit from bot detection and mitigation without any additional configuration or cost.

What's included

• Automated bot detection and scoring — Incoming traffic is automatically evaluated and scored, with managed challenges issued to suspicious requests.
• Verified bot identification — Legitimate bots (such as search engine crawlers) are recognized and allowed through while unverified bots are challenged.

Action Required

Eligible sites will see a banner at the site level in the Pantheon dashboard. To participate in the Beta:

1. Look for the GCDN Beta banner on your eligible site.
2. Click the banner and follow the guided steps.
3. Update your DNS records to point to the new GCDN infrastructure.

During the Beta, DNS-01 TXT record validation is the only supported method for domain verification. You will need to add TXT records to your DNS provider to verify domain ownership.

Known limitations

• Traffic metrics — The traffic metrics page in the Pantheon dashboard will not reflect GCDN Beta traffic during the initial Beta period. Traffic metrics for migrated sites will be restored in a future update.

Eligibility

The following configurations are not eligible for the GCDN Beta at this time:

• Sites using Advanced Global CDN (AGCDN), WAF, or Security Starter packages
• Sites with Multi Zone Failover enabled
• Sites using Custom Certificates

More information

To learn more about the new GCDN Beta with Bot Protection, see our beta documentation page on our docs site.