Yuriy PanovandClaude Opus 5
da93bbc9f3
A deploy that died after mkdir -- a broken build, a missing lock file, a health check that never went green -- left its half-finished release in releases/. That is not just disk: it is the newest directory there, so the KEEP=3 rotation of the next successful deploy counted it among the three to keep and dropped a working release instead, thinning out exactly the rollback targets the runbook tells you to use. The release directory is now armed for cleanup the moment it is created and disarmed once the release is live and healthy, with the removal done by the same EXIT trap that drops the unpacked archive -- so it covers every way out: fatal, a command failing under set -e, an aborted build. The one case left alone is a release the swap did reach and that `current` still points at, i.e. a first-ever deploy with nothing to roll back to: removing that would leave a dangling symlink behind instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>