Skip to main content

Pantheon release notes

Your destination for staying informed about our latest innovations and product updates.
Subscribe to RSS feed

Tools & APIs
November 16, 2026

Starting February 15, 2027, Pantheon will block Terminus versions that have reached end of life (EOL) from connecting to the platform. The initial affected versions are:

Terminus versionEOL dateBlocked starting
4.1.3February 2, 2027February 15, 2027
4.1.1January 29, 2027February 15, 2027
4.1.0November 4, 2026February 15, 2027
4.0.3September 29, 2026February 15, 2027
4.0.2September 11, 2026February 15, 2027
4.0.1September 5, 2026February 15, 2027
4.0.0May 19, 2026February 15, 2027
3.6.2May 7, 2026February 15, 2027
3.6.1March 03, 2026February 15, 2027
3.6.0 or earlierDecember 05, 2025February 15, 2027

Upcoming EOL and block dates for other versions

Versions still in support will be blocked on their EOL date. These dates have already been published and are unchanged:

Terminus versionEOL and block date
4.3.5November 9, 2027
4.3.4November 9, 2027
4.3.3November 3, 2027
4.3.2August 20, 2027
4.3.1June 23, 2027
4.3.0June 2, 2027
4.2.2May 26, 2027
4.2.1May 13, 2027
4.2.0April 30, 2027
4.1.9April 13, 2027
4.1.8April 8, 2027
4.1.7March 30, 2027
4.1.6March 23, 2027
4.1.4March 18, 2027

See Supported Terminus and PHP Versions for the current schedule.

Action required

Upgrade to the latest version of Terminus before February 15, 2027. To check which version you’re running, use terminus --version. For update steps on macOS (Homebrew), Windows and Linux (PHAR), see Install and Update Terminus.

If you are using Terminus in CI with GitHub Actions, we recommend using the Terminus GitHub Action, which always installs the latest version by default.

Why we're making this change

Pantheon set the EOL schedule for Terminus several years ago, but up until now has not enforced the requirement to use supported Terminus versions. Terminus runs on your computer or in your CI environment, so Pantheon can’t remove an old version. Customers who continue to use EOL versions of Terminus cause friction for security and support, as the interaction of some older versions with the platform can be unpredictable. Ensuring that Terminus clients in the field remain up to date will allow Pantheon to strengthen platform security and compliance, and evolve the platform more smoothly.

What happens when a version is blocked?

Commands run with a blocked Terminus version will fail to connect to Pantheon. Newer versions of Terminus will display a message asking you to upgrade. Older versions may not display the message, so automated processes, such as CI jobs, will simply fail until Terminus is upgraded.

What to expect going forward

  • Pantheon will announce each Terminus block at least 90 days in advance and will send reminders multiple times as the block date approaches.
  • Beginning with Terminus 4.3.5, each version will be supported for six months after the next version is released, down from one year. To prevent a newer version from reaching EOL before an older one, new versions will share the previous version's EOL date until the six-month window is reached. After that, the EOL date is the block date.
  • Dates already published are unchanged.
November 10, 2026

Starting Monday, November 16, 2026, Pantheon limits the retention period of manual backups to a maximum of 180 days. Requests for a longer retention period are rejected. This matches the retention options already available in the Site Dashboard, which offers 30 or 180 days.

If you create manual backups with Terminus, update to Terminus 4.3.5 before that date.

What is changing

  • Maximum retention: Manual backups can be retained for at most 180 days. Backup requests that ask for more are rejected.
  • terminus backup:create default: Before Terminus 4.3.5, terminus backup:create retained backups for 365 days when you did not pass --keep-for. Terminus 4.3.5 changes the default to 30 days, in line with the Site Dashboard.
  • Early validation in Terminus 4.3.5: terminus backup:create now checks --keep-for before contacting Pantheon. A value above 180, a value below 1, or a value that is not a whole number stops immediately with a message that explains the allowed range.

Automatic backups and backups created from the Site Dashboard are not affected.

What happens if you do not update

After November 16, 2026, older versions of Terminus still send the 365-day default. As a result:

  • terminus backup:create with no --keep-for option fails.
  • terminus backup:create with --keep-for set above 180 fails.

Scripts and CI pipelines that run terminus backup:create with the default arguments will fail until Terminus is updated.

Action required

  1. Update to Terminus 4.3.5 before November 16, 2026. See How to upgrade.
  2. Review any scripts or CI jobs that call terminus backup:create:
    • If they rely on the default retention, expect backups to be kept for 30 days instead of 365 days after you update.
    • If they pass --keep-for with a value above 180, lower it to 180 or less.

For example, to create a database backup that is retained for 90 days:

Learn more about creating backups.

How to upgrade Terminus

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:

To confirm which version you are running:

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

November 10, 2026

Terminus 4.3.5 is now available. This release points the Terminus account dashboard URL at the dashboard root and changes the default retention for backup:create to 30 days.

Key improvements in this release

  • Shorter default backup retention: backup:create now keeps backups for 30 days by default, previously 365. It also rejects --keep-for values above 180 days, below 1, or that are not whole numbers before contacting the API. The temporary backups created by local:getLiveDB and local:getLiveFiles also now default to 30 days. If your scripts or CI rely on the previous default, pass --keep-for explicitly. (#2934)
  • Account dashboard URL: The Terminus account dashboard URL now points at the dashboard root. (#2944)

How to upgrade to Terminus 4.3.5

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.

November 3, 2026

Terminus 4.3.4 is now available. This release keeps sensitive option values out of request headers and verbose output, fixes dashboard links for multidev environments, and removes a PHP deprecation warning from backup:automatic:info.

Key improvements in this release

  • Sensitive values kept out of headers and verbose output: Terminus no longer includes sensitive option values such as --machine-token, or the arguments of remote commands, in the command header it sends to Pantheon or in very-verbose (-vvv) output. (#2929)
  • Dashboard links for multidev environments: Dashboard URLs, such as those from dashboard:view, now use the site-redirect route, so links to multidev environments resolve correctly. (#2930)
  • Fixed deprecation warning in backup:automatic:info: The command no longer prints a PHP deprecation warning when no automatic backup schedule is set. (#2913)

How to upgrade to Terminus 4.3.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.

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.

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

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.

September 10, 2026

Sites on the Next Generation GCDN can now exempt their own trusted automation from bot protection, without contacting support.

Bot protection on the Next Generation GCDN automatically challenges traffic that looks automated. That is the right default for scrapers and attack tools, but it can also challenge automation you rely on: uptime monitors, CI/CD pipelines, feed importers, and custom API clients that are not on the verified bot list.

You can now generate a bot bypass token for your site using Terminus and configure your automation to send it in the x-pantheon-bot-bypass request header. Requests carrying a valid token skip the standard challenge applied to automated traffic; targeted protections, rate limiting, and the managed WAF still apply to every request.

Key details:

  • Tokens are scoped to a single site (all environments) and valid for 6 months. The command returns a current token and a next token that becomes valid 3 months later; both are accepted during the overlap. Send the current token now, switch to the next token on or after its start date, and re-run the command each quarter to pick up the following pair.
  • Treat the token like a credential. Send it only from trusted servers and services, and never expose it in client-side code. If a token is leaked, contact Pantheon support to revoke it; a replacement token becomes available at the start of the following month.
  • Requests without the header are evaluated by bot protection as usual. Requests with an incorrect token are rejected with a 403, so check the header value first if your automation starts failing.

See Bot Bypass Tokens in the Next Generation GCDN guide for setup instructions.

September 3, 2026

Version 0.9.5 of the 'Push to Pantheon' GitHub Action is now available. This release changes how the action handles a push that has no Pantheon environment to deploy to, and corrects the documentation for the target_env and target_env_strategy inputs.

What's new

A Multidev comes from a pull request. A push to any other branch has nothing to derive an environment name from.

In 0.9.4 the action treated that as an error and failed the job, so adding the action to a workflow that runs on every push would fail on a feature branch with no PR. In 0.9.5 the action skips the remaining steps and the job succeeds, and the step log records why the deployment was skipped.

A misconfiguration still fails the job: a target_env value Pantheon will not accept, an unrecognized target_env_strategy, or the branch strategy with no branch to read.

If you want pushes to other branches to deploy, set target_env_strategy: branch to deploy to a Multidev named after the branch, or set target_env explicitly. (#188)

How to upgrade to 0.9.5

Update your workflow file to use 0.9.5:

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, please use the Push to Pantheon issue queue.