Pantheon release notes

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.

The WordPress Pantheon Advanced Page Cache version 2.1.1 update is now available. This latest update resolves a bug that caused some sites to cache 404 pages, leaving scheduled posts unavailable after publishing.

What's new?

• A post's path is explicitly purged when it is published for the first time, in addition to related surrogate keys.
• Purged paths can be further customized with the pantheon_clear_post_path filter.

Upgrade the plugin now in your WordPress admin to take advantage of these improvements and make the most of Pantheon's edge caching layer or learn more about Pantheon Page Cache in our documentation.

Pantheon has shared our roadmap with customers for a long time, but it was static and didn't allow you to submit feedback. With our new interactive public roadmap, that all changes.

What's new?

• Access our new interactive public roadmap at your convenience.
• Submit feedback about individual features on the roadmap, or new ideas that aren't yet represented.

For more details, see related documentation.

Why is this being done?

In the past, Pantheon’s roadmap was shared via presentations a few times a year. Our hands-on approach with customers isn’t going away, but we wanted to ensure our product roadmap was available to all customers, whenever they needed it. Our prior method also didn’t provide a clear path for feedback, which is now built into the new experience.

What’s next?

Access the roadmap anytime at https://roadmap.pantheon.io. Submit feedback about roadmap items or new ideas that you’d like to see. Help drive the future of Pantheon, ensuring our platform grows with you and continues to meet your needs.

Today we are releasing the side-by-side preview editor for Pantheon's Content Publisher. Previously available by request under a feature flag, the side-by-side preview editor is now available to all users participating in the private beta program.

This new experience makes it easy to see how content from Google Docs will render on your website:

• Edit your Google Doc and see how it renders on your website in a single browser tab - no more juggling multiple windows.
• Get quick access to the preview directly from the content explorer in the administration interface.
• Toggle between ‘desktop’ and ‘mobile preview’ to check responsive rendering.
• Simply change the zoom factor for a better preview if your screen feels too small.

What's next

• Further improvements to this feature as well as other bug fixes and minor improvements will be released continuously.
• See also, the Content Publisher release notes for a more detailed history of changes.

The 1.32.5 update is now available for the WordPress (composer managed) upstream. This quick follow-on release to 1.32.4 extends the previous update that added handling for the index.php file in the web/ directory on composer install actions to composer update as well. Previously, the Composer script maybe-install-symlinks was only run on composer install (Git push). Applying upstream updates would not run this script, which could lead to files being missing from the web/ directory and resulting in your site failing to load.

The 1.32.5 update applies a change to your composer.json file that adds this Composer script to the post-update-cmd Composer hook, ensuring that it runs on all Composer actions (install and update).

For more details, refer to the WordPress (Composer Managed) changelog.

Action required

To benefit from these updates and ensure your site is using the most current version, apply the update to your WordPress (composer managed) site or custom upstream.

The latest version of WordPress, 6.7.2, is available on Pantheon as of February 11, 2025.

Action required

Upgrade to WordPress 6.7.2 directly from your Pantheon dashboard or Terminus to get the latest fixes. For detailed instructions, see related documentation for how to apply core updates.

Highlights

• 35 bug fixes throughout the block editor, HTML API and Customize.

The 1.32.4 update is now available for the WordPress (composer managed) upstream. This release adds handling for situations when the index.php file in the web/ directory is missing or removed. A new check has been added that runs on each composer install (which runs on code sync) that verifies the web/index.php file exists. If it does not, the file is re-created. This prevents an issue where a site would fail to load if that file was missing.

For more details, refer to the WordPress (Composer Managed) changelog.

Action required

To benefit from these updates and ensure your site is using the most current version, apply the update to your WordPress (composer managed) site or custom upstream.