Security1
- Access tokens in Git repository addresses are no longer written to deploy logs
Features9
- Automatic updates: choose off, security fixes only, or all releases. New default is all releases, so panels stay on the latest version
- Server SSH page: manage root's SSH keys, allow root to log in with a key only, and turn password logins off server-wide
- Customers can choose how they log in over SSH: key only, password only, or key or password
- Command-line PHP version per account, used by SSH, the Terminal, cron jobs and background workers
- Mail certificates: the mail hostname and mail.<domain> of every mail domain get trusted certificates automatically, served per name to IMAP, POP3 and SMTP
- Mail Server page shows which certificate mail uses and why; customers see the exact settings for their email apps
- Panel addresses: open the admin and customer panels on a hostname of their own, without a port number
- SSH deploy keys for Git Deploy: generate one or use your own, for private repositories over SSH
- Unlimited option for package limits (sites, domains, subdomains, databases, emails, FTP, cron jobs)
Fixes7
- Deploys now use the site's PHP version for composer and the custom deploy command
- A failed composer install now fails the deploy and leaves the live site untouched; .env and storage/ survive deploys
- Deployment statuses read Live, Building, Queued or Failed, and update on their own
- Mail kept a self-signed certificate after the panel hostname changed; it now follows the mail hostname
- The customer SSH page showed the server's internal name instead of an address that works from outside
- Web templates: the list shows what uses each one, saving re-applies it, and a rejected template is no longer shown as active
- The old Generate deploy key button produced an unusable key; it now works