Patch release fixing two issues found right after v0.3.0 shipped. If you're on 0.2.x or 0.3.0, this is the version to update to.
Fixed
burnless updateno longer rolls back when your instance is running. The post-update health check counted a busy port as a failure — but during an in-place update your current instance is still serving on that port, so the upgrade would roll itself back every time. Port (and a not-yet-generated secrets key) are now treated as informational, soupdatecompletes cleanly whether or not the app is running.burnless startstill refuses a port that's truly taken.- npm package now ships the right build.
burnless@0.3.0was published from a stale build (it reported0.2.1). The publish path now rebuilds and verifies the version before shipping, so the package on npm always matches its label.
Update
burnless update # existing install → 0.3.1
curl -fsSL https://burnless.ai/install | sh # new installVerify the download:
shasum -a 256 -c SHASUMS256.txtFull changes: #16.