Older deployment records and their logs are now retained when the environment cleans up old release directories. You can review past deployment results even after their release files are no longer kept on the server.

A script's execution strategy now lets you choose specific servers. Select the servers that should run the script when deploying the environment, alongside the existing options to run on all servers or a single server.

You can now connect a GitLab account and deploy its repositories. Enable deployment on push for an environment to have repository webhooks trigger deployments when its configured branch changes.

Each environment now has a deployment-trigger URL in its settings. Call it to deploy the configured branch, or select a branch, tag, or commit through the request parameters. You can regenerate the URL when you need to replace it.

You can now arrange connected deployment scripts by dragging them within an environment's deployment steps. Choose whether a script runs on every deployment server or on a single server, which is useful for tasks that should run only once.

Deploy Chief is now available in public beta for deploying PHP applications from GitHub to your servers. Connect a repository, configure environments and SSH servers, then deploy a branch, tag, or commit manually or enable deployments on push.