Pantheon release notes

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.

Composer 2.8.3 is now used in both application containers and Integrated Composer environments.

Automatic rollout - No action required

Composer 2.8.3 will roll out automatically. No action required from you during this process.

Breaking changes

Developers should be aware of a potentially breaking change introduced in 2.8.0. The fallback behavior from https_proxy to http_proxy has been removed, as previously warned in 2.7.3. If your configurations depend on this behavior, update them to avoid connectivity issues.

Highlights

Composer 2.8.3 introduces a range of improvements and updates made between versions 2.7.7 and 2.8.3, including:

• --patch-only flag for updates: Limit updates to patch versions with this new flag for the update command.
• Improved interactive package updates: Enhanced package display makes interactive updates more intuitive.
• JSON schema validation: New validation ensures integrity for composer.lock files.
• PHP 8.4 compatibility: Compatibility updates for the latest PHP version.
• Bug fixes: Resolved issues with provider suggestions and lock file schemas.

View an overview of the changes made between 2.7.7 and 2.8.3 by comparing the tags or explore the highlights on Composer's Releases page.

Notes

• Composer commands can be executed on Pantheon via the Terminus Composer plugin.
• For operations that modify version-controlled code (like adding a module via composer require which will change composer.json and composer.lock), you must run such commands in Dev or Multidev environments where version controlled files are writable. Such files are not writeable in Test and Live environments.
• To learn more about Composer on Pantheon, visit our guide on Integrated Composer.

We’ve added a feature to the billing section of the Pantheon dashboard that helps you quickly check the status of your most recent invoice.

What's new?

• Status tags: Your latest invoice now displays a "Paid" or "Unpaid" tag for easy tracking.

This update makes it easier to stay informed about your latest payment without impacting dashboard performance.

What's next?

This effort towards improved billing visibility in the dashboard lays the groundwork for further improvements down the road. In a future update, we plan to apply "Paid" and "Unpaid" tags across all invoices, rather than just the most recent invoice.

Editorial notes:

• The date of the auto-upgrades has been updated from February 25 to March 12.
• As of January 29, 2025, this release note has been edited to amend the action required. Where previously we required upgrading 5.3 and 5.5 to 7.2 we are now allowing upgrades to 5.6 as well. This can be helpful if you choose to upgrade PHP versions incrementally rather than making the jump to 7.x.

---

As part of our continued effort to protect and secure customer sites, the Pantheon platform will no longer offer PHP versions 5.3 and 5.5 as of March 12, 2025.

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.

We will soon provide long term support (LTS) security coverage for the remaining EOL versions of PHP on the platform.

Action required

Customers with sites using PHP 5.3 and 5.5 should test and upgrade the PHP version to at least PHP 5.6. If no action is taken, sites using PHP 5.3 and 5.5 will be auto-upgraded to PHP 5.6 on March 12, 2025. 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.

Drupal CMS is available to install on Pantheon. Released today by the Drupal Association, Drupal CMS is a new packaging of functionality that combines powerful, user-friendly content creation and management tools with robust flexibility and scalability for developers and end-users alike.

For installation details, check out the new Drupal CMS docs. Please join us in the Pantheon Community Slack or our livestream at 11am Pacific time to celebrate the release!

Our support team is ready and available if you have any questions or issues configuring your new Drupal CMS site.