PHP versions 8.4.22 and 8.5.7 are now available on the platform. PHP 8.5.7 includes security fixes (CVE-2026-44927, CVE-2026-44928) along with bug fixes. PHP 8.4.22 is a maintenance release with bug fixes and stability improvements. Updates will be applied automatically over the next few days, so no manual action is required.
Pantheon release notes
GitLab support for external repositories
Categories:
Pantheon's external repository integration now supports GitLab in addition to GitHub. You can connect a GitLab repository to a Pantheon site via Terminus using --vcs-provider=gitlab, with support for both GitLab.com and self-hosted GitLab instances.
What's new
- GitLab repository support — Create Pantheon sites connected to GitLab repositories using
terminus site:create --vcs-provider=gitlab - Self-hosted GitLab — Connect sites to self-hosted GitLab instances using the
--vcs-host=<your-gitlab-domain>flag - Token-based authentication — GitLab uses legacy personal access tokens or group access tokens rather than OAuth. Tokens require
apiandwrite_repositoryscopes. Group access tokens also require a Maintainer role or higher to create repositories and manage webhooks.
For full setup instructions, see the external repositories documentation.
Security tab now available for Next.js sites
Categories:
The Security tab is now available for Next.js sites in the Site Dashboard. You can password protect any environment with basic authentication, the same way you can for Drupal and WordPress sites. When an environment is locked, visitors are prompted for a username and password before the site is served.
To lock an environment, select the environment, open the Security tab, choose Locked, provide a username and password, and save. To make it public again, choose Public. For step-by-step instructions, see Lock Environments with the Dashboard Security Tool.
Run a new build after changing lock status
On Next.js sites, locking or unlocking an environment does not take effect until a new build is deployed to that environment. After you change the lock or unlock status in the Security tab, trigger a new build using the Rebuild option (available in the Site Dashboard and through Terminus) or by pushing a new commit to the connected branch, so the change is applied to the running site.
For more details about Next.js on Pantheon, see our Next.js documentation.
Terminus 4.3.2 release now available
Category:
Terminus 4.3.2 is now available. This release adds GitLab support for VCS commands, a new --custom-domains flag for drush:aliases, and custom build path support.
Key improvements in this release
- GitLab support for VCS commands:
vcs:connection:addandsite:createnow support GitLab as a VCS provider, enabling customers using GitLab to manage repository connections via Terminus. (#2873) --custom-domainsflag fordrush:aliases: A new flag allows including custom domains in generated Drush alias files. (#2779)- Custom build path support: You can now pass a custom build path when creating sites. (#2851)
How to upgrade to Terminus 4.3.2
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 now supports Bun as a package manager for Next.js sites, alongside npm, yarn, and pnpm. We've also added support for Node.js 26 (LTS).
Bun support
To use Bun, add a bun.lock file to your repository. Pantheon automatically detects the lock file and uses Bun to install your dependencies during the build process.
You can specify a Bun version in the engines.bun or packageManager field of your package.json. If no version is specified, Pantheon defaults to the latest stable release.
Node.js 26 support
Node.js 26 is now available as an LTS runtime for Next.js sites. Set the engines.node field in your package.json to use it:
Node.js 20 removed
Node.js 20 has reached end of life and is no longer available as a runtime. Sites using Node.js 20 must upgrade to Node.js 22 or later.
For more details about Next.js on Pantheon, see our Next.js documentation.
Terminus 4.3.1 release now available
Category:
Terminus 4.3.1 is now available. This patch release makes the --org option required for site:create, enforcing the requirement that all new sites belong to an organization.
Key improvements in this release
--orgnow required for site:create: The--orgoption is no longer optional when creating sites. Previously a warning was displayed; now omitting--orgwill return an error with a clear message. This aligns Terminus with the platform requirement that all sites belong to an organization. (#2845)
How to upgrade to Terminus 4.3.1
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.
Build Tools CI Docker image deprecated
Categories:
We've released the final update to the build-tools-ci Docker image. We will not publish any further updates, bug fixes, or security patches to the following tags:
pantheonpublic/build-tools-ci:9.x-php8.2pantheonpublic/build-tools-ci:9.x-php8.3pantheonpublic/build-tools-ci:9.x-php8.4quay.io/pantheon-public/build-tools-ci:9.x-php8.2quay.io/pantheon-public/build-tools-ci:9.x-php8.3quay.io/pantheon-public/build-tools-ci:9.x-php8.4
Background
These base images were created at a time when CI providers recommend using customized Docker images to speed up execution and reduce the need for replicating boilerplate configration. It has since become more common to run CI jobs on standard base images for speed and the reduction in boilerplate code comes from reusable GitHub Actions or CircleCI Orbs.
Recommended migration
Use a standard base image from your CI provider and install the Pantheon tools you need during the CI run. Standard images are better cached by CI runners, so your pipelines will perform better overall than with a custom image.
Learn more about Pantheon's reusable GitHub Actions and CircleCI Orb.
Action required
If you use any of the build-tools-ci image tags listed above, migrate to a standard base image before the included dependencies become outdated.
Customer Scheduled Jobs is now available to all Pantheon customers. The feature allows you to schedule automated cron jobs tailored to your site's needs — set the frequency (hourly, daily, weekly, or monthly) and the actions to perform, and Pantheon handles execution automatically. Each site has a daily budget of 300 minutes for running jobs.
Previously limited to Early Access participants, the feature is now open to everyone with no enrollment required.
What's changed
- Customer Scheduled Jobs is now available on all eligible sites without Early Access enrollment.
- The Terminus Scheduled Jobs Plugin can be installed and configured on any site.
No action required
If you're already using Customer Scheduled Jobs, your configuration continues to work. New users can install the Terminus plugin and start scheduling jobs immediately.
More information
For setup instructions and usage details, see the Customer Scheduled Cron Jobs documentation.