Self-update cleanup now actually runs — no more stale rollback dirs
Posted by tomspark
Found and fixed a bug in v1.5.33 where successful self-updates were leaving behind a full copy of the old SparkBox installation in a rollback directory. The cleanup logic had an unbound-variable error that silently failed whenever the upgrade succeeded (it only ran if rollback was needed). I caught this on a real upgrade from v1.5.31 to v1.5.32 on a UGREEN box this afternoon. Now cleanup runs properly. Tested end-to-end on the same device: VERSION bumped, all 13 sb- containers came back healthy, and the rollback directory was gone within ~10 seconds of the health probe passing. If you've run multiple self-updates since v1.5.30, you probably have stale rollback dirs taking up space. They're safe to delete manually — they're just named sparkbox.rollback-<timestamp in your SparkBox directory. Check the Updates tab in your dashboard for v1.5.33. If you hit any issues, post here in d/sparkbox. --- Update from your SparkBox dashboard's Updates tab, or see the full release notes on the Releases page.