Pantheon release notes

We have released a new version of the Content Publisher service (back-end + admin interface + Google Docs add-on + CLI + JS SDK v3.11.2).

What's new?

• Authentication tokens: You can now manage tokens from the Content Publisher administration interface settings. Previously, this was partially managed from the CLI.
• Ingest API: This open API allows developers to programmatically ingest content in Content Publisher from other 3rd party services.
• Include in search: New toggle added so you can easily include or exclude content from search.

See also, the Content Publisher release notes for a more detailed history of changes.

PHP versions 8.1.32, 8.2.28 and 8.3.19 are now available on the platform. These updates bring the latest bug fixes and enhancements, improving performance and security for your sites. Updates will be applied automatically over the next few days, so no manual action is required.

Important PHP version information

• PHP 8.1 and 8.2 are currently receiving security-only updates.
• For more details, see the full list of PHP supported versions.

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

As part of our continued effort to protect and secure customer sites, the Pantheon platform no longer offers PHP versions 5.3 and 5.5. Sites currently configured to use PHP 5.3 or 5.5 are being automatically upgraded to PHP 5.6 over the next few days.

PHP 5.5 was declared end-of-life (EOL) by the PHP Foundation on July 21, 2016, more than eight years ago. EOL software does not receive security or feature updates, and could expose sites to attack if any vulnerabilities or exploits are discovered.

Action required

While all sites previously using PHP 5.3 or 5.5 have been auto-upgraded to PHP 5.6, the pantheon.yml file for these sites have not been changed and will still contain the retired values. In the future, this will cause a git push to the platform to be rejected. Customers with sites configured for PHP 5.3 or 5.5 should upgrade the PHP version in pantheon.yml to at least PHP 5.6.

Pantheon currently recommends at least PHP 8.1 for all production sites.

Sites created with custom upstreams using EOL PHP versions may also have unexpected behavior upon site creation.

The Pantheon MU Plugin v1.5.3 update is now available for Composer-based WordPress sites. For non-Composer-based WordPress sites, this latest update will be bundled with the next WordPress core update (likely 6.8, expected April 15.). WordPress (composer managed) sites can upgrade today using composer update or by checking for updates in the dashboard.

What's new?

The 1.5.3 update includes a number of minor bug fixes and enhancements:

• Updates all links to the Plugins with Known Issues documentation page to the updated WordPress Known Issues page to match the update to the docs site.
• Fixes a PHP warning on the Site Health page. (props to Weston Ruter for the report.)
• Fixes an issue in the compatibility layer that was causing the WP Rocket plugin to throw a fatal error on deactivation.
• Updates the compatibility layer to define constants earlier in WordPress execution. Previously, the constants were defined on plugins_loaded which may be too late to override those constants set by the plugins themselves. (props to Rachel Backert for the report.)

The Pantheon Advanced Page Cache and Search API Pantheon modules have been updated to support Drupal 11. This enhancement enables you to confidently launch and manage Drupal 11 sites using these optimized modules.

What's New?

• Drupal 11 Compatibility: Both modules have been tested and updated to ensure seamless integration with Drupal 11, providing enhanced performance and reliability.

Action Required

To take advantage of these updates, please ensure your modules are updated to the latest versions:

• Pantheon Advanced Page Cache: Version 2.3.2
• Search API Pantheon: Version 8.3.1

We recommend reviewing the release notes for each module to understand the specific changes and improvements.

A Terminus 4.0.0-alpha1 pre-release is now available. The next generation of Terminus adds support for PHP 8.4 and removes support for PHP versions 8.1 and below.

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

Support for older PHP versions in Terminus 3.x

Terminus 3.x is not compatible with PHP 8.4. The recommended PHP version to use locally with Terminus 3.x is 8.3.

On macOS with Homebrew PHP 8.3 can be installed by specifying the version when installing the php package, e.g. brew install php@8.3. If you already have PHP installed at the default version (8.4), you may need to use brew unlink php and brew link php@8.3 to use the corrected version.

For more information see the php Homebrew formula.

How to upgrade to Terminus 4.x while in alpha

During the pre-release development phase of Terminus 4, the only way to install Terminus is directly from the phar.

If you previously used Homebrew (macOS-only) to manage your installation, you will not be able to update to Terminus 4 until it is generally available and the Brew formula is updated. In that case, use the commands below to install Terminus to 4.0.0-alpha1:

If you have already installed Terminus via the phar file, you can use terminus self:update --preview to update to the latest version. The --preview flag is required to update to the latest pre-release version of Terminus.

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

Terminus 3.6.2 is now available as of March 03, 2025. This small update contains the latest bug fixes and improvements for this tool.

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

How to upgrade Terminus

If you manage your installation via Homebrew on macOS, you can update Terminus with the following command:

For other systems, see additional upgrade instructions here.

Editorial note: The date for when this change will occur was originally published as March 1, 2025 but has since been updated to March 3, 2025.

To improve API security, New Relic will retire legacy REST API keys on March 3, 2025. These keys are used to access REST API v2 endpoints. To continue to utilize these endpoints, you will need to generate a new API Key. You can read more about this end-of-life in this Forum post.

How to check if you're affected

Not all accounts use REST API keys. To check if you need to take action:

1. In New Relic, click on your profile icon (bottom left) and select API Keys.
2. Click REST API Key on the right side of the page.

This will load the legacy New Relic UI. The following image is an example of an account that does not have a REST API key associated with it.

1. If a key is listed, your account uses a REST API key. If no key appears, your account is unaffected.

The following image is an example of an account that has a REST API key associated with it. Note that when present, you have options to show the key (which will show the first few characters, not the entire key) and delete it.

Tip: REST API keys start with the prefix NRAA or a random combination of letters and numbers.

What to do if you have a REST API key

1. Create a new user API key — this can be done in the New Relic UI or via NerdGraph.
2. Replace the old REST API key with the new user API key in your environment.

What happens if you don’t update your keys by March 3rd?

If you don’t replace the old keys by the deadline, any workflows relying on these keys will stop functioning as intended. Generating a new key and replacing the old key will restore functionality.