v2.9.8

See Why a Git Deploy Failed, Without Digging Through Logs

When a Git deploy fails, the site’s Deployments page now shows which step failed and why. You get one alert when deploys start failing, not one for every failed deploy.

🔥 New Features

🆕 Know Why a Git Deploy Failed

Before, every failed deploy sent you an email with the full deploy log. Finding the real error was hard, and a site that kept failing could fill your inbox.

Who it’s for: Developers who deploy sites from Git.

• On the Deployments page: a Deploys of this site are failing notice shows the failed step, the lines around the first error, and how long the site has been failing.
• One alert per reason: email, Slack, Telegram, WhatsApp and in-app alerts go out when deploys start failing, or fail for a new reason. Repeats are counted, not sent again.
• Shorter alerts: they show the failed step and error lines with a View Deployments link, not the whole log.

Troubleshoot Git deployments that fail, get stuck or don’t trigger

🧑‍💻 For Developers: Public API and MCP

• GET /api/v1/sites/{uuid}/deploy-diagnosis now includes a verdict object for a failed deploy, with its step, error lines and commit.

🐞 Bug Fixes

• Git deploys: Verify connection for a deploy key no longer fails on very large repositories.
• WordPress: installing Redis Object Cache no longer turns off a working cache on sites that are not in English.
• Teams: team admins can manage members again.
• Lovable: projects built with TanStack Start now get their build and start commands filled in for you.
• WordPress updates: a plugin crash during a WordPress update no longer leaves the update stuck.