Pantheon release notes

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:

The Content Publisher MCP Server is now in Public Beta. This integration enables AI assistants and other agentic applications to interact directly with Content Publisher, streamlining content workflows through natural language commands.

The Model Context Protocol (MCP) is an open standard that allows AI assistants and agentic applications to securely connect with external tools and data sources. With the Content Publisher MCP Server, content teams can manage their publishing workflows conversationally -- without leaving their AI assistant interface.

What’s new?

• Connect and manage documents - Connect Google Docs to collections, disconnect documents, and transfer ownership.
• Publish content - Preview, publish, unpublish, and manage approval workflows. Manage all documents metadata.
• Manage collections - Create collections, manage collaborators, administrators and access control, administer webhooks as well as all collection configurations options.
• Work with content model - Manage metadata schemas.

Example workflows

• "Create a Google Doc about our product launch and connect it to the Marketing collection, go through the preview, enrich and publish phase"
• "Update the description metadata for the Q1 report and publish it"
• "Add sarah@company.com as a collaborator on the Documentation collection"
• “Find all documents with Author set at “John Doe” and replace with “Jane Doe”

And really, any other content operation workflow you might think of!

Getting Started

The Content Publisher MCP Server is now in public beta, available to all Content Publisher users. If you are not yet a user, you can sign-up for a free plan on pantheon.io. For instructions on how to install and use, see the Content Publisher MCP documentation.

We welcome your feedback as we continue to improve this integration. Please report any issues through our regular support channels or make feature requests through our Pantheon Roadmap site.

Terminus 4.1.4 is now available. This hotfix release adds PHP 8.5 support and resolves plugin installation issues.

Key improvements in this release

• PHP 8.5 support: Terminus now supports PHP 8.5 (#2769)
• Fixed plugin installation issues: Ensured the plugins composer.json file also disables audit block-insecure, resolving Composer security warnings that could block plugin installation (#2772)

How to upgrade to Terminus 4.1.4

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.3 is now available. This release includes critical fixes for plugin installation issues affecting customer GitHub Actions workflows.

Key improvements in this release

• Fixed Composer security warnings blocking plugin installation: Resolved issues where Composer security audit was preventing Terminus from installing plugins in GitHub Actions environments (#2766)
• Enhanced environment comparison: Fixed logic to not rely on commit labels when comparing environments (#2761)
• Improved session validation: Sessions are now considered active only if they're valid for more than 1 minute (#2758)
• Better error handling: Added proper handling for cases where initialization status isn't returned (#2760)
• Enhanced logging: All logger output messages now include timestamps for better debugging (#2745)

How to upgrade to Terminus 4.1.3

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.

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:

• Log Fowarding Overview
• Sumo Logic Setup
• Splunk Setup

Terminus 4.1.1 is now available. This patch update contains the latest bug fixes and improvements for this tool.

This release includes enhanced database cloning capabilities and improved environment information accuracy.

Added

• Auto-detect URLs for database clone search-replace operations, reducing the need for manual URL configuration when cloning databases between environments

Fixed

• Fixed the drush_version field output in the env:info command to display accurate Drush version information

How to upgrade Terminus

If you manage your installation via Homebrew on macOS, you can update Terminus with the following command:

For other systems, see additional upgrade instructions here.

Terminus 4.1.0 is now available. This minor update contains the latest bug fixes and improvements for this tool.

This release includes enhanced environment information visibility and improved error messaging.

Added

• PHP Runtime Generation and PHP Version fields are now optional fields of the env:list command output, providing better visibility into your environment's PHP configuration
  • Use env:list <site> --fields=id,php_runtime_generation,php_version to view these fields

Fixed

• Improved workflow timeout handling now displays warnings instead of confusing error messages when workflows take longer than expected

How to upgrade Terminus

If you manage your installation via Homebrew on macOS, you can update Terminus with the following command:

For other systems, see additional upgrade instructions here.

Terminus 4.0.3 is now available. This small update contains the latest bug fixes and improvements for this tool.

Added

• Make site label available in site:list and org:site:list commands
• Add a debug log message to workflow:wait printing the workflow start time

Fixed

• Regression affecting SSH commands (e.g., drush, wp-cli) on sites using external version control
• Un-deprecated --tags parameter on org:site:list command
• Remove unnecessary api call from tag:add and tag:list causing unnecessary load and timeouts

How to upgrade Terminus

If you manage your installation via Homebrew on macOS, you can update Terminus with the following command:

For other systems, see additional upgrade instructions here.