Pantheon release notes

Pantheon Search now supports Apache Solr 9.10.0 as a Beta for Drupal 10 and 11 sites. This is available through search_api_pantheon version 8.5.0-beta1, which supports both Solr 8 and Solr 9.

What's new?

• Added Solr 9 support.
• Solr 9 brings improved security defaults, the unified highlighter, and other enhancements. See the major changes in Solr 9 for details.
• Bumped Search API Solr version requirement to 4.3.x.

Getting started with Solr 9 (Beta)

Upgrading from Solr 8 to Solr 9

1. Update the module:

   Commit and deploy the changes to your Pantheon environment.

2. Update your pantheon.yml:

   Commit and deploy the changes to your Pantheon environment.

3. Clear the cache:

4. Post the schema for the new Solr version:

5. Clear the index and reindex content:

6. Test search functionality thoroughly and report any issues in the drupal.org issue queue.

New installations

To try the Beta with Solr 9 on a new site, set the Solr version in your pantheon.yml and install the module:

For detailed setup steps, see the documentation.

What about Solr 8?

Solr 8 (8.11.4) remains fully supported. Existing Solr 8 sites can update to Search API Pantheon 8.5.x without any configuration changes.

Older Drupal versions

Pantheon Search is no longer supported for Drupal 8-9.3 as of December 2, 2025.

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

Feedback and documentation

Bug reports, feature requests, and feedback should be posted in the drupal.org issue queue. For detailed installation and upgrade instructions,Pantheon Search documentation.

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.

Version 1.0.5 of the Pantheon Content Publisher Drupal module is now available. This release includes bug fixes and feature improvements.

What's new?

• Approval workflow support — Content Publisher Drupal module now supports approval workflow, allowing administrators to review and approve the content before publishing.

For more details, refer to the release notes.

The Drupal CMS upstream has been updated to version 2. Newly created sites using the Drupal CMS upstream will now use Drupal CMS 2, which includes a curated set of modules and configuration designed to help you get started faster.

This update only applies to sites created with the Drupal CMS upstream. Sites using the Drupal 10 or Drupal 11 upstreams are not affected. Existing Drupal CMS sites are also not affected — refer to the Drupal CMS documentation for upgrade guidance.

Our documentation has instructions on how to configure a new Drupal CMS site.

Pantheon's Solr search Drupal module, search_api_pantheon, has been updated with two new releases — 8.4.0 and 8.4.1. These releases include significant architectural improvements and enhanced developer experience.

We recommend upgrading directly to 8.4.1.

What's Changed in 8.4.0

• License corrected to GPL-2.0+ to align with Drupal standards.
• Major code refactoring resulting in a 60% reduction in code length.
• Simplified service architecture for better maintainability.
• Removed unnecessary overrides for Guzzle, Endpoint, and the Solarium client.
• Improved local development experience. Server connector configuration fields are now editable in local environments and automatically overridden when deployed to Pantheon.
• Drush commands automatically use the first enabled server with the Pantheon connector. The server_id argument is no longer needed or accepted.
  • For more details, see the diagnostic commands section in README.md: https://git.drupalcode.org/project/search_api_pantheon/-/blob/8.4.x/README.md#diagnostic-commands

Dependency Updates:

• Removed direct dependencies on guzzlehttp/guzzle, symfony/finder, symfony/yaml, and other packages now provided transitively through search_api_solr (these dependencies are still available but come through search_api_solr instead).
  • Impact: No action required unless custom code directly uses these services
• Removed kint-php/kint dependency.

What's Changed in 8.4.1

• Restored the search_api_pantheon_admin submodule (removed in 8.4.0) as an obsolete module to support smooth upgrades from earlier versions.

Action Required

1. Back up your database before proceeding with the upgrade.
2. Test thoroughly in a non-production environment before deploying to your live site.

Pantheon Search Server Migration

Since version 8.3.0, the default server ID is pantheon_search. New installations use this automatically. Existing sites upgrading from earlier versions can migrate from pantheon_solr8 to pantheon_search via an update hook.

If you proceed with migration, the update hook will update the server ID from pantheon_solr8 to pantheon_search, reassign all indexes to the new server, and flag content for reindexing.

After running database updates (drush updb), reindex your content:

To opt out of migration and continue using pantheon_solr8, add this to your settings.php before running database updates:

Upgrade Instructions

For detailed installation and upgrade instructions, please refer to:

• README.md
• CHANGELOG.txt

Important: Version Support

Version 8.4.x is now the only maintained version; support for 8.3.x and 8.2.x has been discontinued.

The latest update to the Pantheon Advanced Page Cache Drupal module includes a change regarding module compatibility to ensure the best performance for your site.

Key Update

The BigPipe module is fundamentally incompatible with the architecture of Pantheon's Global CDN and the functionality provided by Pantheon Advanced Page Cache module. To improve site reliability, the module will now automatically disable BigPipe when Pantheon Advanced Page Cache is enabled.

If the BigPipe module is somehow enabled after PAPC is installed, a clear error message will now be displayed on the Drupal Status Report page (/admin/reports/status).

This warning clearly highlights the fatal incompatibility and the risk of site errors.

The following updates are now available for Content Publisher:

• New release of the Pantheon Content Publisher v1.0.3 Drupal module now availabe.
• With Approval Workflows enabled, Administrators now have the option to Approve submissions direclty from the Pending approval tab of a Collection in the Content Dashboard. Previously, opening each submission in Preview mode was required.
• The experience for Smart Components has been improved for first time users.
• Upgrade Content Publisher AI metadata suggestion to use Gemini 2.5 flash instead of Gemini 2.0.
• Bug fix for our Next.js starter kit and SDK to properly support Next.js 15.5 and the use of App Router. Improve the build process by using pinned versions of dependencies.
• Fix several event tracking issues in the back-end.

Editorial note: The date has been moved from January 19 to January 26.

Tika 1.18 and 1.21 will no longer be available starting January 26, 2026. Impacted sites must upgrade to Tika 3.2 which is available via PHP Runtime Generation 2.

The Apache Tika toolkit detects and extracts metadata and structured text content from various documents using existing parser libraries. On the Pantheon platform, our customers tend to use Tika to parse PDF content for searching with Solr.

Action Required

For most customers, we expect the upgrade to be seamless and not require any manual intervention. But if your site has a custom Tika integration, we recommend you follow our documentation for upgrading to Tika 3 as soon as possible to ensure your site continues to operate as expected.

Sites which have not upgraded to Tika 3 as of January 26, 2026, will be automatically upgraded. Setting tika_version: 1 in pantheon.yml will be ignored after that date. Symlinks from the 1.xx jar filepaths (/srv/bin/tika-app-1.xx.jar) will point to the new Tika 3 jar (/opt/pantheon/tika/tika.jar). These symlinks will be removed later in 2026.