Pantheon release notes

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:

Terminus 4.1.7 is now available. This hotfix release fixes the domain:verify command to properly display DNS challenge details.

Key improvements in this release

• domain:verify fix: Fixed the command to display DNS challenge details when a domain is unverified, and added polling for verification status after triggering verification (#2797)

How to upgrade to Terminus 4.1.7

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.2.0-rc.1 is now available as a pre-release. This release candidate merges several standalone plugins into Terminus core and adds Elasticsearch support with unified search commands.

Key improvements in this release

• Secrets Manager plugin merged into core: The terminus-secrets-manager-plugin is now built into Terminus (#2764)
• Repository plugin merged into core: The terminus-repository-plugin is now built into Terminus (#2792)
• Node Logs plugin merged into core: The terminus-node-logs-plugin is now built into Terminus (#2791)
• Elasticsearch support: New search:enable and search:disable commands for managing search indexing (#2783)
• Bug fix: Empty body should be object, not array (#2780)

How to install Terminus 4.2.0-rc.1

This is a pre-release version intended for testing. To install it directly from the .phar file, you can download it from the GitHub release page.

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.6 is now available. This release adds the domain:verify command, new Elasticsearch search commands, and deprecates the legacy Solr commands.

Key improvements in this release

• Domain verification command: New domain:verify command allows users to verify domain ownership directly from Terminus (#2790)
• New search commands: New search:enable and search:disable commands for managing search indexing services (#2783, #2784)
  • Note: These commands are currently non-functional for WordPress until Elasticsearch platform compatibility is added
• Solr command deprecation: solr:enable and solr:disable are now deprecated in favor of the new search:enable and search:disable commands
• Bug fix: Fixed empty body handling to use object instead of array (#2780)

How to upgrade to Terminus 4.1.6

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.

Pantheon Content Publisher now supports Microsoft Word thanks to our new Microsoft Add-in. This add-in allows organizations and teams to publish content directly to their website from their Microsoft 365 account in Microsoft Word.

What's new?

• Write, edit, collaborate, and publish from Microsoft Word (online and desktop app) to your website
• Preview how your content will look before it goes live
• Collaborative editing: Use comments, suggestions, and other collaboration features available on Microsoft 365

Documentation

Learn how to set up Content Publisher on your Drupal, WordPress, or Next.js website:

• How to install the Office 365 it
• Publishing with the Microsoft Word add-in
• Content Publisher general documentation

Content Publisher now includes a quality assistant — an intelligent review system that helps you create better content before you publish. Starting with accessibility checking at no added cost, the quality assistant will expand to help ensure your content meets brand standards, performs well in search, and satisfies compliance requirements.

What’s new?

The quality assistant's automatic accessibility checking helps catch common issues before you publish:

• Missing alt text on images
• Improper heading hierarchy
• Non-descriptive link text
• and more...

Issues are displayed in the sidebar with plain-language descriptions of the problem, why it affects users with disabilities, how to fix it, and where it occurs in your document.

For more information, see the quality assistant in the Content Publisher documentation.

We have released version 0.8.0 and version 0.9.0 of the 'Push to Pantheon' GitHub Action.

What's new in 0.8.0?

Version 0.8.0 adds several new features and improvements to the GitHub Action.

• Git-only deployment - You can now deploy directly to Pantheon using Git push without requiring Terminus Build Tools. Set skip_build_tools: true to use this lightweight deployment option, which is ideal for brand-new sites or workflows that don't need database or file syncing.
• Automatic Build Tools fallback - The action now automatically falls back to Git-only mode when Build Tools operations fail, ensuring deployments succeed even when the Build Tools plugin encounters issues. This fixes a failure mode where deploys would fail if a site did not yet have a Live environment initialized.
• Multidev limit checking - The action now checks if you've reached Pantheon's multidev limit before attempting to create environments, providing clear error messages when limits are reached instead of cryptic failures.
• GitHub permission validation - New pre-flight permission checks validate that your GITHUB_TOKEN has the required scopes before starting deployments, with helpful error messages explaining how to fix missing permissions.
• Build Tools version selection - You can now choose which version of the Terminus Build Tools plugin to install using the build_tools_version input parameter. This gives you control over plugin compatibility and allows testing development versions if a particular Build Tools version or branch is required.

What's new in 0.9.0?

Version 0.9.0 adds a number of under-the-hood improvements and moves much of the scripting logic out of the action.yml file and into a new main.sh file. This makes the action easier to maintain and test, and also allows for more complex logic that would be difficult to implement directly in the action.yml file.

Additionally, version 0.9.0 adds comprehensive unit and integration tests for the actions logic and deployment workflows, improving the reliability and stability of the action. The new testing framework also allows for easier debugging and faster development of new features in the future.

For more details and a full list of changes in these releases, please refer to the 0.8.0 release notes and 0.9.0 release notes.

To update to the latest version, modify your workflow file to use 0.9.0: