Anthony 9f02e0faf2 ci(deploy): preempt self-update timer so it can't starve the deploy lock ... The self-update systemd timer redeploys from source (no SKIP_BUILD) and can hold setup.sh's flock for >5min while compiling on a tiny droplet. When it fires close to a CI push it starves the deploy, which waits the full 5min on the lock and then fails with 'another setup.sh run is in progress (lock held >5m)'. The CI push is authoritative (ships prebuilt binaries + resets to the exact commit), so stop any in-flight timer run to release the lock and pause the timer before taking it. setup.sh re-enables the timer at the end of its run. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-01 08:27:58 +00:00
..
ci.yml	chore(deps): bump the github-actions group with 4 updates (#70)	2026-07-01 01:08:44 -07:00
deploy.yml	ci(deploy): preempt self-update timer so it can't starve the deploy lock	2026-07-01 08:27:58 +00:00
mailu-update.yml	chore: keep all agentbbs services on latest software (#69)	2026-06-30 20:06:06 -07:00
test.yml	chore(deps): bump the github-actions group with 4 updates (#70)	2026-07-01 01:08:44 -07:00
vu1nz-scan.yml	chore(deps): bump the github-actions group with 4 updates (#70)	2026-07-01 01:08:44 -07:00