Pantheon release notes

Terminus 4.1.3 is now available. This release includes critical fixes for plugin installation issues affecting customer GitHub Actions workflows.

Key improvements in this release

• Fixed Composer security warnings blocking plugin installation: Resolved issues where Composer security audit was preventing Terminus from installing plugins in GitHub Actions environments (#2766)
• Enhanced environment comparison: Fixed logic to not rely on commit labels when comparing environments (#2761)
• Improved session validation: Sessions are now considered active only if they're valid for more than 1 minute (#2758)
• Better error handling: Added proper handling for cases where initialization status isn't returned (#2760)
• Enhanced logging: All logger output messages now include timestamps for better debugging (#2745)

How to upgrade to Terminus 4.1.3

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.

Teams using Pantheon's Secrets Manager to set variables like API tokens can now do so through the site dashboard. Previously this feature only had a command line user interface through a Terminus plugin. Secrets Manager works with WordPress, Drupal, and Next.js sites hosted on Pantheon. It does not work with the sunsetting Front-End Sites product.

Secrets Managers encrypts values at rest and then makes them available to your application's code as it runs. Secrets Manager is suitable for setting variables that are truly sensitive like a password, token, or key that allows Next.js to read from a back-end CMS as well as variables that might not be sensitive like a Google Tag Manager ID.

What's new?

• Create new site-owned secrets from the site dashboard
• Create new site-owned secrets in bulk from the site dashboard by either:
  • manually adding multiple keys at once of the same type and scope
  • or importing secrets from .env files (e.g., Next.js sites)
• Manage existing site-owned secrets from the site dashboard:
  • Edit default secret value and/or secret scope
  • Add/edit/delete environment overrides

For details, see related documentation.

We are pleased to announce that all of our actively maintained WordPress plugins are now confirmed fully compatible with WordPress 6.9.

Actively Maintained Plugins

The following plugins have been tested and verified for compatibility:

• WP SAML Auth
• Pantheon Advanced Page Cache
• Pantheon HUD
• Native PHP Sessions
• Pantheon Content Publisher
• WP Redis

Action Required

We recommend updating your Pantheon plugins to their latest versions alongside your WordPress 6.9 core upgrade. This ensures you receive the latest performance optimizations, security patches, and full compatibility with PHP 8.4.

As a best practice, always test these updates in a Dev or Multidev environment before deploying to Live.

Pantheon has released a new version of our WP SAML Auth WordPress plugin. This update focuses on modernizing PHP support and providing developers with more granular control over SAML configurations.

What's New

• PHP 8.4 Compatibility: Full support for PHP 8.4 has been added.
• Updated PHP Requirements: The minimum supported PHP version has been increased to 7.4 to ensure better security and performance.
• WordPress 6.9 Compatibility: Confirmed compatibility with WordPress 6.9.
• Enhanced Configuration: Added the wp_saml_auth_internal_config filter, allowing developers to customize the OneLogin SAML configuration.
• SimpleSAMLphp 2.x Support: Improved auto-detection for SimpleSAMLphp 2.x and optimized autoloader discovery to skip redundant processes when the SimpleSAML\Auth\Simple class is already loaded.

Bug Fixes

Settings Page Warnings: Fixed a warning message on the plugin's settings page that appeared for users not utilizing SimpleSAML.

Important: Compatibility & Testing

While this update improves autoloader discovery, it changes how the plugin interacts with the local environment. We strongly recommend testing in a lower environment before upgrading especially if you use:

• Non-Standard Installations: Custom SimpleSAMLphp installations located in non-standard directories.
• Manual Autoloaders: Custom autoloader code that manually handles the loading of SimpleSAMLphp.

Action required

We encourage you to upgrade to the latest version of WP SAML Auth as soon as possible to take advantage of the latest features and compatibility updates. updating to get the latest features and compatibility updates.

If you have questions or concerns, please open issues in the queue for the plugin.

New sites created on the Pantheon platform now default to Tika 3.x. Previously, new sites defaulted to Tika 1.x.

This change only affects newly created sites. Existing sites will continue to use their current Tika version and are not impacted by this update.

Overriding the default

If you need to use Tika 1.x for a new site, you can explicitly set the version in your pantheon.yml file:

However, Tika 1.x will be removed on January 26, 2026. We recommend testing your site with Tika 3.x and migrating before this date.

More information

• Apache Tika on Pantheon
• Tika 3.2 now available
• Tika 1.x end of life

PHP versions 8.3.30 and 8.4.17 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.

PHP 8.3.30 is available on both PHP Runtime Generation 1 and PHP Runtime Generation 2.

PHP 8.4 is only available with the new PHP Runtime Generation 2.

The PHP Foundation officially considers PHP 8.1 as End Of Life status as of December 31, 2025.

However, Pantheon includes LTS security coverage for all available PHP versions with PHP Runtime Generation 2. This coverage is automatic and requires no further action. By providing LTS editions of older PHP versions, customers can safely operate their sites while working through upgrade plans to modern versions.

For the best performance and security, Pantheon recommends running PHP 8.2 and above.

The final set of sites previously excluded from the PHP Runtime Generation 2 rollout are now being migrated. These sites were excluded because they were using Solr 3 with Drupal 9+. With Solr 3 support for Drupal 9+ ending in December 2025, these sites are no longer excluded from the Generation 2 rollout.

Rollout Timeline

Opting Out

Sites may continue to opt out of PHP Runtime Generation 2 until the Gen 1 removal takes place starting April 6, 2026.