Skip to main content
​
September 27, 2026

​
A failed build no longer loses your new application

When dependency installation or the build command failed while creating an application, the creation failed and the upload was discarded — and the error that explained why was never shown.Now the application is created anyway, stopped (status: "down"), with the install or build output in its logs:
  • Dashboard: after the upload you land on the application, with the build error in the console. Fix the files in the file manager and start it again — no need to upload the project again.
  • API, SDKs and CLI: POST /v1/apps returns 201 with the application in down instead of an error. BUILD_FAILED, BUILD_TIMEOUT, INSTALL_FAILED, INSTALL_TIMEOUT, INSUFFICIENT_MEMORY and INSTALL_SHIELD_BLOCKED are still returned (422) when starting or restarting an existing application.
  • The application counts toward your plan’s application limit like any other stopped application.

​
Bun 1.2.23

Bun applications now run on 1.2.23, the recommended and latest version. Versions 1.2.2 and 1.1.0 are no longer offered: their official images are built on an operating system release that stopped receiving security updates.
  • Applications without VERSION, or with VERSION=recommended, move to 1.2.23 on their next start or restart.
  • If your vertracloud.config pins VERSION=1.2.2 or VERSION=1.1.0, change it to 1.2.23.