Skip to main content

Pantheon release notes

Your destination for staying informed about our latest innovations and product updates.
Subscribe to RSS feed
New feature
December 11, 2025

Log forwarding for Splunk and Sumo Logic is now availble via a Private Beta program. There is no additional cost for this feature and anyone can request an invite by submitting this form.

For more information, see this related blog post.

When enabled, this feature streams the following log types from your Pantheon site to your external service (Splunk or Sumo Logic):

  • php-fpm-error
  • php-slow
  • php-error
  • nginx-access
  • nginx-error

Share feedback: Once Beta access has been granted, users will recieve a welcome email and be invited to a dedicated slack channel where you can provide feedback, ask questions and discuss usage with the Pantheon product and engineering team.

To request an invite, submit this form.

Documentation

See also, the following new docs:

December 10, 2025

The new Site Dashboard is now available for all Workspaces. Today's release switches Personal Workspaces over to the new experience, a change we recently completed for Professional Workspaces.

The following ON/OFF toggles have been removed from the user interface:

  • Personal Workspace > Site list "Open sites in new beta"
  • Professional Workspace > Site list "Open sites in new beta" (removed in a previous release)
Information:
Note

The following highlights what users can expect in the new experience. Note these items have not been added or impacted by todays change but were delivered by our earlier Beta release.

  • Same functionality, familiar workflows – No need to relearn anything. Your day-to-day tasks remain unchanged.
  • Modern, accessible design – We’ve made significant improvements to align with the latest usability design standards, enhancing readability, contrast, and navigation.
  • Performance improvements under the hood – While this may feel mostly visual, we’ve reworked key infrastructure for long-term speed and reliability.
  • Small but powerful UX upgrades – New conveniences like one-click to copy the commit SHA, along with other thoughtful touches for enhanced usability.

Shows a preview of the new/fresh commit log

November 18, 2025

Today, Pantheon's new solution for Next.js enters Private Beta. To request an invite, submit this form.

Front-End Sites, our previous offering for Next.js, will be discontinued. We encourage users to migrate to the updated architecture.

For more information, see this related blog post.

What's new?

Some key changes for Next.js on Pantheon include:

  • Improved runtime architecture, including support for Pantheon's Global CDN.
  • Site creation via the command line or the dashboard.
  • Sites listed in your workspace alongside WordPress and Drupal, instead of a separate tab.
  • Unified site dashboard design that's consistent with WordPress and Drupal user interfaces: The Pantheon dashboard showing a dev environment for a Next.js site

For more detailed information on the differences from Front-End Sites, see our migration guide.

Documentation

For usage instructions and guidance, see the following new docs:

November 18, 2025

Starting today, the new Site Dashboard enters General Availability for Professional Workspaces. Specfically, this release changes the following for Professional Workspaces:

  • The new experience is now the default, previously it could be enabled and disabled.
  • The option to disable the new experience has been removed.

Personal Workspaces are not impacted, and still require opting in to enable the new experience.

Information:
Note

The following highlights what users can expect in the new experience. Note these items have not been added or impacted by todays change but were delivered by our earlier Beta release.

  • Same functionality, familiar workflows – No need to relearn anything. Your day-to-day tasks remain unchanged.
  • Modern, accessible design – We’ve made significant improvements to align with the latest usability design standards, enhancing readability, contrast, and navigation.
  • Performance improvements under the hood – While this may feel mostly visual, we’ve reworked key infrastructure for long-term speed and reliability.
  • Small but powerful UX upgrades – New conveniences like one-click to copy the commit SHA, along with other thoughtful touches for enhanced usability.

Shows a preview of the new/fresh commit log

August 20, 2025

A new beta experience for a freshly modernized Site Dashboard is rolling out across the platform starting now and will be available to all users over the coming weeks. Sign up now to skip the wait!

Enable the new beta experience

Once rolled out, users will be prompted to toggle this new beta experience from the site list of a given Workspace:

Shows a site list for a professional workspace, with a banner at the top to toggle the new beta experienec off/on for site dashboards

When the toggle is “on,” the new beta experience of the site dashboard will be enabled. All site dashboards opened from this view will use the new beta experience.

Information:
Note

Please note the toggle setting is specific to each user. If multiple users have access to the workspace, the toggle’s setting (on /off) will NOT impact others.

What to expect

  • Same functionality, familiar workflows – No need to relearn anything. Your day-to-day tasks remain unchanged.
  • Modern, accessible design – We’ve made significant improvements to align with the latest usability design standards, enhancing readability, contrast, and navigation.
  • Performance improvements under the hood – While this beta may feel mostly visual, we’ve reworked key infrastructure for long-term speed and reliability.
  • Small but powerful UX upgrades – New conveniences like one-click to copy the commit SHA, along with other thoughtful touches for enhanced usability.

Shows a preview of the new/fresh commit log

Other details

  • Sections in progress – A few parts of the dashboard are still in development and will roll out over the course of the beta program:
    • Site team
    • Domain management
    • New Relic
  • Easily switch back – If you need to, you still have access to the current dashboard.
  • Share feedback – We have a dedicated Slack channel for beta participants where you can easily ask questions and discuss feedback with the Pantheon product and engineering team. To request an invite, submit this form.
July 15, 2025

Support for PHP 8.4 is now available on the platform with the new PHP Runtime Generation 2. PHP 8.4 is the latest version of the server-side language powering Drupal and WordPress.

CMS support

PHP 8.4 is recommended for sites running Drupal 10.4+ or 11.1+. See the Drupal PHP requirements documentation for more details.

WordPress 6.7+ only has "beta support" for PHP 8.4, therefore Pantheon does not recommend using WordPress in a production environment with this PHP version yet.

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

New features

PHP 8.4 is not expected to bring new performance gains for sites. But for developers looking to take advantage of the latest PHP functionalities, a few new updates are notable:

  • Property Hooks: Introduces support for computed properties, allowing for pre/post-processing of values.
  • Asymmetric Visibility: Provides independent control over property read/write scope.
  • Enhanced DOM API: Adds new classes for HTML5 parsing.
  • New Array Functions: Introduces array_find(), array_find_key(), array_any(), and array_all().
  • PDO Driver Subclasses: PDO now includes driver-specific subclasses.
  • Updated JIT: Includes a new implementation of the Just-In-Time compiler.
  • Expanded String Functions: New mb_trim(), mb_ltrim(), mb_rtrim(), mb_ucfirst(), and mb_lcfirst() functions.

See the PHP 8.4 release announcement from php.net for full details.

How to upgrade

To upgrade your site, set the following in your pantheon.yml file:

Note: PHP 8.4 is only available with the new PHP Runtime Generation 2. Upgrading to PHP 8.4 will automatically upgrade the environment to the second generation PHP Runtime.

May 16, 2025

Today we releasing a new "Push to Pantheon" GitHub Action. This Action provides a reusable step so that, in a few lines of yml, teams using GitHub Actions and Pantheon together can push their code from GitHub to Pantheon inside of a larger workflow that they control.

This Action is designed to create a Multidev environment environment for each pull request:

Deploying a PR to a Pantheon Multidev

Here is the configuration that would go within a .github/workflows/deploy-pr.yml file to accomplish this workflow.

The Action can push code to the Pantheon Dev environment upon pull request merges (or direct pushes to a main branch).

Deploying main to Pantheon

See the readme file within the repository for full usage instructions.

While this Action is already in use on live websites we recommend testing it thoroughly with your own sites before fully relying on it. Prior to the 1.0.0 release, we recommend that only teams with pre-existing continuous integration experience adopt this Action. In addition to this Action that is meant for teams interested in customing their Continuous Integrations workflows, we are also developing a direct GitHub Integration meant for simplicity.

For questions and support, please use the issue queue on the repository. For more background on why we made this Action and how it fits in our ecosystem, see this blog post from Director of Developer Relations, Steve Persch.

May 15, 2025

Today we are making a new GitHub Application for direct integration with Pantheon available as a private Beta. Let us know here if you would like access to this GitHub Application turned on for your Pantheon workspace.

Similar to our recently released Action, this GitHub Application also moves code to Pantheon Multidev environments and the Dev environment to correspond to changes made to a repo on GitHub.

Diagram of the GitHub Application process of deploying a PR to a Pantheon Multidev

This Application is intended for teams that want the simplest possible tool for achieving the above workflow. Once it is turned on, no additional configuration is necessary.

The GitHub Action is intended for teams who want to make customization to their workflows and treat the deployment of code as one step in a larger Continuous Integration workflow.

More information