Pantheon release notes

Terminus 4.2.2 is now available. This release adds object cache and search visibility to site:info, upstream fields to site listing commands, and Node.js dependency update support.

Key improvements in this release

• Object Cache and Search status in site:info: site:info now shows whether Object Cache (Redis) is enabled and which search index (Elasticsearch, Solr, or both) is active (#2812)
• Upstream fields in site:list: site:list and org:site:list now support upstream and upstream_label as optional --fields values (#2835)
• Node.js dependency updates: upstream:updates commands now support Node.js sites for dependency management (#2828)
• EVCS site creation validation: Site creation for EVCS sites now uses server-side repo name validation for more accurate error messages (#2831)
• PHP 8.2 fix: Resolved deprecation warnings for dynamic property creation in the Site model (#2813)

How to upgrade to Terminus 4.2.2

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

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

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

We've made it easier to auto-instrument New Relic Browser Agent monitoring on Drupal 10.2+ sites.

Starting in Drupal 10.2, strict Content-Length headers were introduced that broke New Relic's standard Browser Agent auto-injection. You can now re-enable browser monitoring with a single pantheon.yml setting, and Pantheon's platform will handle the injection automatically. Changes take effect within a few minutes.

WordPress sites and Drupal versions prior to 10.2 are unaffected. Browser Agent auto-instrumentation continues to work out of the box for those frameworks.

For full details, visit our documentation page on New Relic.

Terminus 4.2.1 is now available. This patch release fixes a pagination bug affecting org:site:list and a WordPress-specific issue.

Key improvements in this release

• Fix incomplete site listings: org:site:list could return truncated results when the API returned short pages, affecting organizations with sites in supporting workspaces (#2829)
• WordPress fix: Only include wp_replace_siteurl if the site is WordPress (#2825)

How to upgrade to Terminus 4.2.1

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

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

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

Support for creating Drupal and WordPress sites using an external repository on GitHub is now generally available to Pantheon customers with Gold, Platinum or Diamond Workspaces. Previously, this capability was restricted to a private beta program; now, it is included as part of the recent Terminus 4.2.0 Release.

Sites created on an external GitHub repository utilize a GitHub Application that moves code to Pantheon Multidev environments and the Dev environment when correspond to changes are made to on that repository.

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.

Pantheon continues to offer a GitHub Action that performs a similar function 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.

See our Github application documentation page for more instruction on usage and a breakdown of limitations.

Terminus 4.2.0 is now available. This minor release brings major improvements including three integrated plugins and enhanced Node.js/STA site support.

Key improvements in this release

• Integrated core plugins: Three popular plugins are now built directly into Terminus, eliminating the need for separate installation:

  • terminus-secrets-manager-plugin for managing secrets (#2764)
  • terminus-repository-plugin for repository management (#2792)
  • terminus-node-logs-plugin for Node.js build logs (#2791)

• Enhanced Node.js/STA site management:

  • node:builds:wait command for tracking STA site deployment progress (#2798)
  • node:builds:rollback command for easy build rollbacks (#2803)
  • Enhanced builds:list with active build status (#2807)
  • Added deployment status to builds command (#2801)
  • Improved site creation workflow by skipping dev environment wait (#2810)
  • Node.js sites can now use the metrics command (#2806)

• Bug fixes:

  • Update check in env:wake for node sites (#2816)
  • Update Node.js site creation notice to reflect actual build trigger (#2819)

How to upgrade to Terminus 4.2.0

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

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

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

Terminus 4.1.9 is now available. This patch release fixes SSH output formatting issues and resolves env:wake command failures.

Key improvements in this release

• SSH output formatting fix: Resolved an issue where SSH command output would appear garbled when streaming, improving terminal display readability. (#2814)
• env:wake command fix: Fixed env:wake failures by removing the unnecessary X-Pantheon-Styx-Hostname header requirement, allowing environments to wake successfully. (#2815)

How to upgrade to Terminus 4.1.9

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

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

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

Terminus 4.1.8 is now available. This patch release adds a warning when creating sites without specifying an organization, ahead of the Q2 2026 requirement that all sites belong to an organization.

Key improvements in this release

• site:create --org warning: Warns users when site:create is called without the --org option, and provides a clear error message if the backend rejects the request. The --org option help text now indicates the upcoming requirement. (#2786)

How to upgrade to Terminus 4.1.8

If you use Homebrew (macOS-only) to manage your Terminus installation, you should upgrade using:

If you installed Terminus directly from the .phar file, you should upgrade using the self:update command:

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

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

We have renamed Personal Workspaces to My Dashboard and have removed the ability to create new sites directly within it. Going forward, all new sites must be created within a Professional Workspace.

For details on workspaces, including how to create a free Professional Workspace, see related documentation.

What's changing?

• The Personal Workspace has been renamed to My Dashboard throughout the Pantheon dashboard.
• Site creation:

  • In the dashboard, the option to select a Personal Workspace during site creation has been removed. Users must now select a Professional Workspace when creating a new site.

  • From the commandline, running terminus site:create without the --org flag returns this wanring:

    An org must be defined to create a site.

    Sites created via Terminus without an org are added to your My Dashboard workspace.

What's not changing?

Existing sites associated with My Dashboard are not affected. This update to the dashboard site creation process only prevents new sites from being added.

Site creation via Terminus without an org will still complete successfully at this stage. No changes to your existing Terminus scripts are required yet.

Looking ahead

Starting June 1, 2026, specifying an org will be required when creating sites via Terminus. We recommend updating your scripts now to avoid disruption: