Deploy Chief now emails team members when a deployment fails or succeeds. Each member chooses which emails they receive for a team under Deployment notifications in settings. Failure emails are on by default, and success emails are off until you turn them on.

The deployment log now summarizes the deployment in its header and updates its status live. Step output appears inline and opens automatically for failed steps. Steps skipped after a failure are marked, and when every step ran on the same server, the steps appear as a single list.

Open Search or jump with Cmd+K or Ctrl+K, then search for an application or script to go straight to it. Results are scoped to your current team.

Open the app switcher beside the Deploy Chief name to move between Chief Tools apps. You can also open it with Cmd+J or Ctrl+J.

Use the theme control in your account menu to choose Light, Dark, or System. System follows your device’s appearance setting.

Deployment scripts can now read $DEPLOY_CHIEF_SERVER_USER to find the SSH username used for the current server. The value reflects an environment's custom user when one is configured.

Set a custom server user in an application's environment to run deployments with that SSH account. Environments without an override continue using the server's configured user.

Deployment step output now renders ANSI colors and formatting. Open a deployment's steps to read formatted command output and distinguish messages that use terminal styling.

Deployments can now run on servers without PHP installed when the application does not need it. PHP-specific preparation and Composer installation steps are skipped when the corresponding tools are unavailable, so deployment scripts can support other application stacks.

Add an integration for your self-hosted GitLab instance and connect its repositories to Deploy Chief. Configure the GitLab application for your instance and provide its HTTPS URL when setting up the connection.

You can now connect more than one application to the same repository, allowing separate deployment configurations for the same codebase. When connecting GitHub, choose which available installation to link to the team.

You can now roll back to an earlier deployment by activating its existing release on your servers. The target release must still be present on the servers; a rollback reuses that release rather than building it again.

You can now start a fresh deployment using the same commit and environment as an earlier deployment. Use Redeploy when you need to run the deployment again without selecting the commit manually.

New environments now show a setup checklist with links to configure settings, prepare the .env file, set deployment scripts, and run your first deployment.

Deployment scripts now receive DEPLOY_CHIEF_APP_URL and DEPLOY_CHIEF_DEPLOY_URL. Use these environment variables to include links to the application page and deployment log in your own notifications or integrations.

You can now save a Url in an environment's settings. A link appears beside the environment name so you can open the deployed website directly; the URL is also included when creating its GitHub deployment record.

Enable Sync deployment status to GitHub in an environment's settings to report deployment progress and results to its GitHub repository. The deployment status includes a link back to the Deploy Chief log. This option is available for GitHub applications and requires the integration to have deployment permissions.

You can now configure a custom PHP executable for an environment. Deployment scripts use that executable for the php command, including tools that locate PHP through their script launcher, so environments can deploy with different installed PHP versions.

You can now connect a Bitbucket account, select one of its repositories, and deploy it to your servers. The integration also supports repository webhooks for deployments triggered by pushes.

Deployment scripts now load the SSH user's .bash_profile before running. Commands can use the environment variables and PATH configured there, which helps when deployment tools are installed in user-specific locations.