Skip to main content

Pantheon release notes

Your destination for staying informed about our latest innovations and product updates.
Subscribe to RSS feed
April 10, 2024

The latest version of WordPress, 6.5.2, became available on Pantheon as of April 10, 2024.

Highlights

What happened to 6.5.1?

6.5.2 is the first minor release for WordPress 6.5 rather than 6.5.1. Yesterday, it was disclosed on the Make WordPress Core development site that due to an error with the initial package, 6.5.1 could not be released.

Upgrade to WordPress 6.5.2 right from your Pantheon dashboard or Terminus for added security.

April 3, 2024

We are thrilled to announce that on April 23, 2024, we will upgrade the New Relic PHP agent to the latest version (v10.19.0.9). This update is part of our ongoing commitment to enhancing your experience with Pantheon and ensuring that our offerings meet your evolving needs.

By staying up-to-date with the latest agent, you will benefit from improved performance and enhanced troubleshooting capabilities for your WordPress and Drupal instances. This means smoother experiences for your site visitors and more efficient workflows for you. This new version also fully supports PHP 8.3, providing you with the latest features and compatibility.

Learn More about New Relic®, real-time performance monitoring for your Pantheon web applications.

Action Required: Default behavior of New Relic Drupal Hooks is changing

After the release of this agent update, Pantheon will no longer support Drupal Hooks reporting by default. However, the functionality is still available. If this is crucial for troubleshooting your sites, please add these lines to your site’s pantheon.yml file to enable this reporting:

The parameter above will take effect when the New Relic PHP agent is updated for your site.

If your site currently reports Drupal Hooks information to New Relic, you will need to add the above line to your pantheon.yml file before the April 23 update to maintain this reporting moving forward.

Our support team is happy to help if you have any questions or need assistance.

April 2, 2024

The latest version of WordPress, 6.5 (Regina), became available on Pantheon as of April 2, 2024.

Highlights

Font Library

  • WordPress 6.5 introduces the new Font Library. This feature allows you to upload fonts to your WordPress site or install any of the fonts available from Google's font library.
  • Previously, in version 1.3.3 of our Pantheon MU Plugin, we added support for the new Font Library feature by explicitly defining where fonts are stored to support this new feature.
  • For more information, refer to our documentation.

Interactivity API

  • WordPress 6.5 also adds a new Interactivity API. This API establishes a standardized way to add interactive elements to Gutenberg blocks.

Performant Translations

  • A new localization system has been introduced in WordPress 6.5 to improve the performance of translations. This system uses a new file format, .l10n.php, to store translations in addition to the standard .mo and .po files you may already be familiar with. When .l10n.php files exist, they are loaded instead, providing significant performance improvements and using less memory.
  • For more information about Performant Translations on Pantheon and how to generate .l10n.php files if they do not exist, see our Performant Translations guide.

Plugin Dependencies

  • WordPress plugins can now have dependencies on other plugins. This allows plugin authors to specify that their plugin requires another plugin to be installed and activated in order to work properly. A new Requires Plugins Plugin Header has been introduced to require other plugins to be installed and activated before the current plugin can be activated and prevent plugins that are dependent upon other plugins to be deactivated accidentally. For more information, see the Plugin Dependencies dev note.

...And More

March 28, 2024

What is changing?

Great news! Pantheon is simplifying the way we calculate and apply site visit overages. This change will help reduce excess billing and unplanned costs should a site exceed its plan limits.

This change is effective for site visits on or after January 1, 2024. In order to transition to the new overages model and allow you, the customer, to digest this change Pantheon will not run an overages process in February 2024. This new program will be formally launched in March 2024 and the initial month’s processing will encompass usage from January and February of 2024.

The new overage charge policy

Effective for usage starting on January 1, 2024, overages will be billed $40 for each 10,000 unique site visits (a unique site visit is defined as a specific IP address and user agent combination over a 24-hour period) or portion thereof that exceeds the amount of included unique visits in the subscription. This applies uniformly to all sites running on the platform at all subscription levels.

In addition, with Overage Protection, all Pantheon customers, except for Basic plans and monthly subscriptions, will have one month of overages waived every 12 months during the subscription term. For simplicity, the 12-month period will follow a calendar year running from January through December. This Overage Protection will be applied automatically on the first month of each plan year where your site is over the included unique visits in the subscription- you do not have to do a thing.

Lastly, for new customers coming onto the platform for the first time there will be a three-month grace period starting with your service start date (the day a site is first moved from a Sandbox to a commercial plan) where no overages will be incurred. This allows you the time to get calibrated on the platform and focus on what is most important: the successful launch of your web site(s) on Pantheon!

The prior overage charge policy

Prior to this change, if a site exceeded the unique site visits included in the subscription plan, the plan would be automatically upgraded to a higher plan level that was a better fit for the amount of unique site visits. Many times that increase would result in a surprise to customers, who hadn’t budgeted for increasing the plan for the remainder of the subscription term, and the cost would be more than what customers thought was fair. We listened, and we’re making this change to make Pantheon a brand you trust even more.

Will you show me an example of how this works?

Example scenario

Assume you purchase an annual Performance Small plan that includes 25,000 unique monthly site visits starting October 1st. The cost of a Performance Small plan is $160 per month (paid annually). Note that the next plan level up is a Performance Medium plan that includes 50,000 unique monthly site visits is $275 per month (paid annually).

During the holiday season, you have 40,000 unique site visits in November and 45,000 in December, before returning to less than 25,000 monthly unique site visits during the rest of your contract term (Jan-Sep).

Dataset for example overage scenario

Overage fee under the new policy

Under the new policy, you will simply pay a one-time fee of: $ 0 for November’s extra 15,000 visits because Overage Protection allows 1 free month of overages, and $ 80 for December’s extra 20,000 visits.

Overage fee under the old policy

Because you exceeded the plan limits of 25,000 for two consecutive months, under the old policy your plan would have been automatically upgraded to the Performance Medium plan starting in December. This would have increased your monthly cost from $160 to $275 a month, or an additional $115 per month. Since the plan change occurred in December and you still had 9 months remaining on your term, this increase would have cost $1,035 extra, which would be charged to your credit card in January or you would have received an additional invoice for plans on contract.

Comparison of the new vs. old overage fee

As you can see in this example, the new overage fee is a total of $80 vs. the cost for the upgraded plan under the prior policy would have increased your cost $1,035 –- the new policy saves you 92%!

Chart comparing price difference between the old policy and new policy

Updated documentation

We've updated our Overage Policy documentation to align with the new policy and provide more specifics, such as additional benefits for new site launches and qualifying nonprofit organizations.

March 27, 2024

On March 25, 2024, it was announced in the WordPress development blog that the default storage location for the Font Library (added in WordPress 6.5) will be wp-content/uploads/fonts. Previously, we had added a feature to our Pantheon MU Plugin to support the new Font Library feature by changing the previous default path (wp-content/fonts) to wp-content/uploads/fonts. This change to our MU plugin removes that override as it is no longer necessary. You can read more about the Font Library feature in our guide to using the Font Library on Pantheon.

March 26, 2024

We've updated our Terminus GitHub Action with the ability to share sessions across jobs to simplify and reduce the authentication overhead including any associated rate limiting when authenticating their machine token. These sessions are encrypted prior to being cached using industry standard AES-256 encryption, PBKDF2 (Password-Based Key Derivation Function 2) algorithm, and increased iterations when deriving the encryption key. We've also updated to the latest versions of actions/checkout and actions/cache.

Some technical details:

  • The session data is encrypted using OpenSSL with AES-256 and PBKDF2 before being cached.

  • The session information is scoped to a workflow run, meaning re-running the same workflow will use existing cache (in case of a failure, etc) while new workflows create a new session.

March 26, 2024

The Pantheon Advanced Page Cache Module has received an update in the 2.2.0 release which resolves Issue #3337669 and provides some additional enhancements. Now, when any file is updated inside the Drupal File system, that file will have its edge cache cleared immediately and new content will be shown.

Some Technical Details:

  • The cache clearing is specifically triggered by any action which invokes the update file hook.

  • If the file is an image, all image styles will also have their edge cache entry cleared.

March 20, 2024

As part of our continued effort to provide the latest and best in secure software, PHP versions 7.1 and below will reach end-of-sale (EoS) on May 15, 2024. This means that sites created after May 15 will not be able to change their PHP version to PHP 7.1, 7.0, or any version of PHP 5. Sites created with custom upstreams using EoS PHP may also have unexpected behavior upon site creation.

Sites already running PHP 5, PHP 7.0, or PHP 7.1 will continue to run even after May 15.

PHP 7.1 was declared end-of-life (EoL) by the PHP Foundation on November 30, 2020, more than three years ago. PHP 5.6 reached EoL on December 31, 2018, more than five 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

Customers using custom upstreams with a PHP version less than 7.2 should update their custom upstreams by May 15 to avoid disruption. The current supported versions of PHP are 8.1, 8.2, and 8.3. Pantheon currently recommends at least PHP 8.1 for all production sites.