skiff.git/internal/lock, branch master Unnamed repository; edit this file 'description' to name the repository. https://git.mikeanthonywild.com/skiff.git/atom?h=master 2026-08-08T00:02:40Z Add per-app flock locking around deploy, config change, rollback, new-app 2026-08-08T00:02:40Z Claude noreply@anthropic.com 2026-08-08T00:02:40Z urn:sha1:acde3827f60bc90738429fa490a36a1856a93283 Nothing previously serialized these against each other, so concurrent invocations for the same app (a manual config change racing an in-flight deploy, a double git push, a rollback mid-deploy) could interleave snapshot/apply/restart/rollback sequences against the same dataset and jail. The lock file lives under a new LocksDir, outside any per-app ZFS dataset, since those datasets get rolled back on a failed health check or a manual rollback.