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
November 17, 2026

The Pantheon MCP Server now supports three more AI clients. You can connect them to operate on your Pantheon fleet through the same governed, user-authorized access introduced in the Pantheon MCP Server (Beta) release and expanded in Additional AI Client Support.

What's included

Pantheon MCP now supports these AI clients:

  • Gemini
  • Devin (formerly known as Windsurf)
  • Cursor

Authorization stays with Pantheon: the server forwards your own Pantheon identity, so an agent can only reach what you can already access.

Who it's for

Developers and teams who want to manage Pantheon sites and environments through the AI client they already use, while keeping control of what agents can change.

How to get started

Add the Pantheon MCP server in your preferred client and sign in with your normal Pantheon account. To disconnect and log out, remove the Pantheon MCP connection in your client.

For client-specific setup steps, see related documentation.

Availability

All Pantheon customers. For feedback, please sign up for the Pantheon Community Slack here. If you already have an account, join us in the #beta-mcp-server channel.

November 9, 2026

The Pantheon MCP Server now supports more AI clients. You can connect the clients below to operate on your Pantheon fleet through the same governed, user-authorized access introduced in the Pantheon MCP Server (Beta) release.

What's included

Pantheon MCP now supports these AI clients:

  • Claude AI and Claude Code
  • ChatGPT
  • Codex
  • GitHub Copilot
  • Google Antigravity

Authorization stays with Pantheon: the server forwards your own Pantheon identity, so an agent can only reach what you can already access.

Who it's for

Developers and teams who want to manage Pantheon sites and environments through the AI client they already use, while keeping control of what agents can change.

How to get started

Add the Pantheon MCP server in your preferred client and sign in with your normal Pantheon account through the OAuth flow. To disconnect and log out, remove the Pantheon MCP connection in your client.

For client-specific setup steps, see related documentation.

Availability

All Pantheon customers. For feedback, please sign up for the Pantheon Community Slack here if you don't already have an account and join us in the #beta-mcp-server channel.

November 6, 2026

This release makes editing across Workstreams clearer, improves Block behavior and navigation, and fixes setup and dashboard issues.

P1 repository and dashboard (https://content.pantheon.io), P1 clients (p1-next-sdk 0.26.0, css-client 0.26.0, puck-css 0.26.0)

Editor improvements

  • Open Live drafts from any Workstream: A page created on Live but not yet published can now be opened from another Workstream. The editor shows Live’s draft with a clear banner. Nothing is saved to the Workstream until you make the first edit; that edit creates the Workstream’s own version.
  • Clear sign-in authorization feedback: If you sign in with an account that is not authorized for a Site, the editor now displays a “Not authorized” screen and offers the option to sign in with a different account.
  • History stays up to date: The History panel refreshes the version list each time it opens while keeping the current list visible during the refresh.

Block Library improvements

Links, forms, cards, and controls now behave as expected across the blog, card, integrations, marketplace, team, event, webinar, and footer Blocks, as well as the documentation shell.

  • Link fields use their configured destinations instead of defaulting to #, and whole Block cards link to their page.
  • Block forms submit to their configured action URL.
  • Search, filtering, pagination, and navigation controls work across the updated Blocks.
  • Embeds and replay videos render from a source field.
  • In the component library, controls that are unavailable in preview now explain why.

Starter-kit and dashboard fixes

  • More reliable setup with npm and yarn: Scaffolding with the P1 Block Library no longer fails dependency installation with ERESOLVE. If installation still fails, the final message explains that Block registration was skipped and provides the commands to complete it.
  • Page Settings title saves correctly: Changes to a page title now persist to the correct page setting.
November 3, 2026

Sites on the Next Generation GCDN can now exempt trusted tools from bot protection by their User-Agent, without contacting support.

Bot bypass tokens cover automation you can configure to send a request header. Some tools can't do that: hosted uptime monitors, SEO scanners, accessibility scanners, and partner integrations often let you see or set their User-Agent but not add a custom header.

You can now use Terminus to add up to 8 User-Agent strings to each of your site's domains. Requests whose User-Agent header exactly matches one of a domain's entries skip the standard challenge for automated traffic on that domain. Targeted protections, rate limiting, and the managed WAF still apply to every request.

Key details:

  • Entries apply to a single domain. The domain must be a verified custom domain on the Next Generation GCDN, and you must have access to the site to manage its entries. If a tool requests both example.com and www.example.com, add the entry to each. Wildcard domains are not supported. To manage entries, use terminus gcdn:ua-bypass:add, gcdn:ua-bypass:remove and gcdn:ua-bypass:list.

  • Matching is exact and case-sensitive against the full User-Agent string, including any version number. If a tool changes its User-Agent, for example after an upgrade, update the entry.

  • A User-Agent is not a secret: any client that sends the same string also skips the challenge. Prefer a distinctive string that identifies your tool. Entries that look like a web browser's User-Agent are refused unless you confirm with --allow-browser-ua. If your automation can send a request header, use a bot bypass token instead.

  • Changes take effect within a few minutes. Remove entries you no longer need.

Update the plugin with terminus gcdn:update, or install it with terminus self:plugin:install pantheon-systems/terminus-gcdn-plugin. gcdn:update can't upgrade version 0.4.0 or earlier: run terminus self:plugin:uninstall pantheon-systems/terminus-gcdn-plugin, then install it again.

For setup instructions, see User-Agent Bypass in the Next Generation GCDN guide.

November 2, 2026

This release improves the P1 editor experience, speeds up page listings on larger sites, makes localization easier to adopt in existing projects, and strengthens MCP request handling.

Released: P1 Collaborative Content Repository (CCR), P1 Dashboard (https://content.pantheon.io), P1 clients (p1-next-sdk 0.25.0, css-client 0.25.0, puck-css 0.25.0 p1-media: 0.5.2)

Editor improvements

  • Clearer state after page deletion: When the page open in the editor is deleted, the canvas now clears and displays a “This page was deleted” message with a way back to the site. Publish is disabled for the deleted page.
  • Faster page creation: The new-page dialog opens with focus in the Page title field, so you can start typing immediately.
  • Consistent editor appearance: Editor controls, popovers, and toasts keep the light theme when the host site uses a dark theme.
  • More reliable focus mode: Pressing Esc exits focus mode after the canvas reloads, but does not exit while a canvas menu or dialog is open.
  • Faster page listings: Page lists load more efficiently on large sites, including when filtering by path.
  • Site thumbnail: P1 site thumbnails can now be manually updated in the dashboard.
  • Clearer localization language: Site Structure now uses “locale” instead of “market.”

Localization and starter-kit updates

  • Localization support provided out-of-the-box by the starter kit: The starter kit now scaffolds a site with localization support ready to use, including default path for localized url, no more need to build localization in your project.
  • Move an existing project to localized pages: The P1 Next.js SDK migration command now supports named migrations. To enable localized pages in an existing starter project, run:

The editor-layout migration is available as migrate editor-layout.

  • Clearer starter configuration guidance: The starter kit’s .env.example now explains when to leave P1_SITE_URL unset.

MCP security and request handling

  • MCP requests are handled statelessly and use the token supplied with each request.
  • MCP tokens, authorization headers, and session IDs are no longer written to logs.
  • MCP tokens cannot access API-key management or account-management routes.
October 30, 2026

Version 0.9.7 of the Push to Pantheon GitHub Action is now available. This release adds inputs that control what a new Multidev clones from its source environment, and makes the target_env input more forgiving about capitalization.

What's new

  • Control what new Multidevs clone: Two new optional inputs, clone_files and clone_database, control what the action copies from source_env when it creates a Multidev. Both default to true, so existing workflows behave as before. Set either to false to skip that content (the action passes --no-files or --no-db to terminus multidev:create). This is useful when a Multidev only needs code, or when cloning a large database or files directory slows down every pull request. The inputs only apply when the action creates the Multidev. They have no effect on a Multidev that already exists. They also don't apply when the action deploys with Terminus Build Tools, which creates the Multidev itself. In that case the action logs a warning if either input is set to false. (#199)
  • Uppercase target_env values are lowercased: Pantheon environment names must be lowercase. In 0.9.4 through 0.9.6, a target_env with uppercase letters failed the deployment with a message that the name was not a valid Pantheon environment. The action now lowercases the value and logs a message noting the change. Other naming problems, such as underscores, and reserved names like master, are still rejected. Branch names longer than 11 characters are still truncated to a maximum of 11 characters. (#200)

Example

This workflow step creates new Multidevs with code only, without copying the database or files from the source environment:

How to upgrade to 0.9.7

Update your workflow file to use 0.9.7:

For more information about this release, see the GitHub release page. To learn more about deploying to Pantheon from GitHub, see GitHub Actions.

If you have questions or concerns about the action, ask in Pantheon Community Slack or use the Push to Pantheon issue queue.

October 30, 2026

Pantheon now provides a Drupal 12 upstream for testing. New sites created from it start on the latest Drupal 12 release, currently 12.0.0-beta2, with PHP 8.5 and MySQL 8.4.

Drupal 12 is still in beta, so use it for testing, not for production sites. Drupal 12 compatibility for Pantheon's modules is in progress. The Drupal core release schedule plans the release candidate (12.0.0-rc1) for the week of November 9, 2026, and the stable release (12.0.0) for the week of December 7, 2026.

Create a Drupal 12 site

Create a site with Terminus:

Drupal 12 does not appear in the dashboard's site creation flow yet, so use Terminus.

Known issue: error after installing

After you install Drupal 12, you may see this error from Drupal core:

If you see it, clear the cache:

October 21, 2026

This release brings a way to "unpublish" content, in other words, to take pages offline, more control over localized content URLs, clearer dashboard experience for Business Account and better editorial experiences as well as hardening across P1 APIs, Workstreams, permissions, and authentication.

New features and improvements

Unpublish: take pages down from Live without deleting them

P1 can now take a published page offline while keeping its content as an editable draft. Editors can publish the page again when it is ready, and the unpublish event remains visible in page history with the actor and timestamp. The capability is available in the editor, public API, and MCP tools, with the same permission checks across each surface.

Unpublishing can include child pages, translated child pages, or only the specific child pages selected by the editor. Each page can also have its own redirect target while it is offline.

The editor can optionally send visitors to another page while an unpublished page is offline. The Site Structure also identifies pages that are currently down with a view-only draft tag.

More predictable localization

Sites can now control how newly created translations are named and routed: in a locale folder such as /fr-fr/slug, or beside the Source page such as /pricing.fr-FR. The default route being now  /{locale}/slug . Existing translation paths remain unchanged when the setting changes.

Translation creation through the API and MCP now respects the locales a site publishes. Agents can see the published locale list and offer only supported choices, while existing translations remain unaffected if a site later stops publishing a locale.

Clearer editor and Business Account experiences

  • Canvas edit and delete controls now align with the approved interaction design across desktop, tablet, mobile, and dark mode.
  • Locked blocks now respect Member permissions in the editor, and template writes are protected consistently across REST, realtime, MCP, and agent paths.
  • The open Visual Editor refreshes its Workstream list when another user creates a Workstream.
  • Workstream terminology is now used consistently in chatbot responses and dashboard notifications.
  • Long Workstream names no longer hide the Review/Publish control.
  • Version History date headers and editor rail tooltips now layer correctly while scrolling.
  • Content Publisher add-on slug edits no longer show the P1 dashboard redirect prompt.
  • Agent edits now show the registered agent’s name and appropriate agent styling instead of always appearing as Zappy.
  • The editor no longer remounts the canvas when the AI chat feature flag resolves.
  • Organization members can be assigned the Viewer role, and backend site roles now consistently map to Admin, Member, and Viewer.
  • Business Account setup now returns users to the dashboard after naming their account, and account search matches owner email addresses.

Component library and starter-kit improvements

  • Installed P1 blocks can be registered automatically from their registry metadata instead of requiring manual import and category edits.
  • The starter kit now respects the package manager used to invoke it and avoids silently selecting an incompatible scaffolder version on supported Node releases.

Fixes, security, and reliability

Safer cross-site and cross-Workstream authorization

P1 now tightens authorization and resource scoping across Workstreams, Structures, merge requests, merge previews, and published-content tokens. Requests cannot use identifiers from another Site to read or change structures, merge requests, merge targets, or Workstream data.

Additional platform work migrated the CCR router to Hono, consolidated domain boundaries around core entities, and fixed merge-job claim handling after create collisions.

Creating or moving a page onto a redirect source path no longer leaves the new page silently shadowed by the redirect.

Stronger authentication and Business Account isolation

  • Broker login redemption is being protected against redeeming a transaction approved by a different user.
  • MCP authorization now requires explicit user consent and stronger PKCE handling before returning an authorization code to a client.
  • Agent presence access now checks both Business Account membership and whether the requested agent belongs to that account.
  • Dependency vulnerabilities identified in pantheon-content-cloud were remediated across the tracked package updates.

Publishing, realtime, and operational fixes

  • Realtime sync no longer persists an empty snapshot as a document version unless the user explicitly cleared the document.
  • Dashboard toasts no longer sit underneath the Zendesk support widget.
  • Slow CCR database statements are now logged at useful thresholds without logging statement text or customer content.
  • Retired feature-flag code paths, configuration, and tests were removed after replacement behavior was confirmed.
  • The monitor dashboard now provides a view of monitor status and Site health.

Internal validation and enablement

  • Auth0 authentication coverage was added through NextAuth validation.
  • The Collaboration System design and prototype spike was completed.