Pantheon release notes

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.

The latest version of WordPress, 6.9.1, is available on Pantheon as of February 4, 2026.

Action required

Upgrade to WordPress 6.9.1 right from your Pantheon dashboard or Terminus to access the latest features, fixes, and security enhancements. See related documentation for how to apply core updates.

Highlights

• This minor release includes fixes for 49 bugs throughout Core and the Block Editor, addressing issues affecting multiple areas of WordPress including the block editor, mail, and classic themes. For a full list of bug fixes, please refer to the release candidate announcement.

WordPress 6.9.1 is a short-cycle maintenance release. The next major version of WordPress will be 7.0; it is scheduled for release on 9 April 2026 at WordCamp Asia.

For full details about WordPress 6.9.1, see the official release announcement.

A new user interface is now available in the Metrics tab of the Live environment of site dashboards, named Top traffic patterns which reports the following new traffic metrics:

• Top IP addresses
• Top user agents
• Top visited URL paths

With this data, you can identify aggressive crawlers or scrapers, that you may want to block manually or prioritize caching and optimization efforts based on the specific pages receiving the highest request volume.

Note: This data includes both counted and uncounted visits.

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.

Key Changes: CLI Rename

We've renamed the Content Publisher CLI from pcc to cpub to reflect our product naming. This change affects all CLI commands and the associated NPM package.

CLI Command

• Old: pcc
• New: cpub

NPM Package

• Old: @pantheon-systems/pcc-cli
• New: @pantheon-systems/cpub-cli

Action Required

Please update your existing commands by replacing pcc with cpub. All flags and arguments remain the same. Deprecated pcc CLI still functional with warning messages.

To update your installation:

1. First, log out of the old CLI:

2. Uninstall the old package:

3. Install the new package:

4. Login to the new CLI:

Additional Changes

• Connected Accounts are no longer tied to the user’s browser and has been migrated to server-side account management improving overall user experience
• Dashboard now displays user account subscription and usage allowing users to keep track of their account usage limits
• A search function has been added to the Collections dropdown in the Tokens modal for easier navigation in workspaces with many collections
• The App Router starter kit default installation no longer uses Static Site Generation (SSG)
• Minor bug fixes and UX improvements

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.

Teams using Pantheon's Secrets Manager to set variables like API tokens can now do so through the site dashboard. Previously this feature only had a command line user interface through a Terminus plugin. Secrets Manager works with WordPress, Drupal, and Next.js sites hosted on Pantheon. It does not work with the sunsetting Front-End Sites product.

Secrets Managers encrypts values at rest and then makes them available to your application's code as it runs. Secrets Manager is suitable for setting variables that are truly sensitive like a password, token, or key that allows Next.js to read from a back-end CMS as well as variables that might not be sensitive like a Google Tag Manager ID.

What's new?

• Create new site-owned secrets from the site dashboard
• Create new site-owned secrets in bulk from the site dashboard by either:
  • manually adding multiple keys at once of the same type and scope
  • or importing secrets from .env files (e.g., Next.js sites)
• Manage existing site-owned secrets from the site dashboard:
  • Edit default secret value and/or secret scope
  • Add/edit/delete environment overrides

For details, see related documentation.

We are pleased to announce that all of our actively maintained WordPress plugins are now confirmed fully compatible with WordPress 6.9.

Actively Maintained Plugins

The following plugins have been tested and verified for compatibility:

• WP SAML Auth
• Pantheon Advanced Page Cache
• Pantheon HUD
• Native PHP Sessions
• Pantheon Content Publisher
• WP Redis

Action Required

We recommend updating your Pantheon plugins to their latest versions alongside your WordPress 6.9 core upgrade. This ensures you receive the latest performance optimizations, security patches, and full compatibility with PHP 8.4.

As a best practice, always test these updates in a Dev or Multidev environment before deploying to Live.