PHP versions 8.2.32, 8.3.32, 8.4.23, and 8.5.8 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.
Elasticsearch is now available as an add-on for WordPress sites on Pantheon for all Performance sites and above. This new capability is powered by ElasticPress, the leading Elasticsearch solution for WordPress.
ElasticPress improves the overall search experience and performance of your WordPress sites, as well as allowing for better WP_Query performance and reduced load on your application server. Capabilities include:
WP_Query integration — ElasticPress allows you to offload WP_Query requests to Elasticsearch, reducing database load and improving page load times.Elasticsearch is available to WordPress sites on Performance Small plans and above.
Review the Setup and Configuration documentation for detailed instructions on setting up Elasticsearch and ElasticPress.
For additional guidance and a walkthrough of these features, see the Elasticsearch on Pantheon documentation.
Pantheon Search now supports Apache Solr 9.10.1 for Drupal 7, 10, and 11 sites, with improved security defaults, the unified highlighter, and performance enhancements. See the major changes in Solr 9 for details.
Solr 9 support is available through Search API Pantheon version 8.5.0.
For detailed setup instructions, see the Solr for Drupal 10/11 guide.
Solr 9 support is available through the Pantheon Drupal 7 upstream version 7.105.1.
For detailed setup instructions, see the Solr for Drupal 7 guide.
The previously announced removal schedule still holds:
Report issues or provide feedback in the drupal.org issue queue for Drupal 10/11, or through Pantheon Support for Drupal 7.
PHP versions 8.4.22 and 8.5.7 are now available on the platform. PHP 8.5.7 includes security fixes (CVE-2026-44927, CVE-2026-44928) along with bug fixes. PHP 8.4.22 is a maintenance release with bug fixes and stability improvements. Updates will be applied automatically over the next few days, so no manual action is required.
Pantheon's external repository integration now supports GitLab in addition to GitHub. You can connect a GitLab repository to a Pantheon site via Terminus using --vcs-provider=gitlab, with support for both GitLab.com and self-hosted GitLab instances.
terminus site:create --vcs-provider=gitlab--vcs-host=<your-gitlab-domain> flagapi and write_repository scopes. Group access tokens also require a Maintainer role or higher to create repositories and manage webhooks.For full setup instructions, see the external repositories documentation.
The Security tab is now available for Next.js sites in the Site Dashboard. You can password protect any environment with basic authentication, the same way you can for Drupal and WordPress sites. When an environment is locked, visitors are prompted for a username and password before the site is served.
To lock an environment, select the environment, open the Security tab, choose Locked, provide a username and password, and save. To make it public again, choose Public. For step-by-step instructions, see Lock Environments with the Dashboard Security Tool.
On Next.js sites, locking or unlocking an environment does not take effect until a new build is deployed to that environment. After you change the lock or unlock status in the Security tab, trigger a new build using the Rebuild option (available in the Site Dashboard and through Terminus) or by pushing a new commit to the connected branch, so the change is applied to the running site.
For more details about Next.js on Pantheon, see our Next.js documentation.
Terminus 4.3.2 is now available. This release adds GitLab support for VCS commands, a new --custom-domains flag for drush:aliases, and custom build path support.
vcs:connection:add and site:create now support GitLab as a VCS provider, enabling customers using GitLab to manage repository connections via Terminus. (#2873)--custom-domains flag for drush:aliases: A new flag allows including custom domains in generated Drush alias files. (#2779)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.
Pantheon now supports Bun as a package manager for Next.js sites, alongside npm, yarn, and pnpm. We've also added support for Node.js 26 (LTS).
To use Bun, add a bun.lock file to your repository. Pantheon automatically detects the lock file and uses Bun to install your dependencies during the build process.
You can specify a Bun version in the engines.bun or packageManager field of your package.json. If no version is specified, Pantheon defaults to the latest stable release.
Node.js 26 is now available as an LTS runtime for Next.js sites. Set the engines.node field in your package.json to use it:
Node.js 20 has reached end of life and is no longer available as a runtime. Sites using Node.js 20 must upgrade to Node.js 22 or later.
For more details about Next.js on Pantheon, see our Next.js documentation.
Our Documentation is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Code snippets are additionally licensed under The MIT License.