v1.44.2
fix(update): prevent the background auto-updater from spawning runaway npm install -g processes.
Under concurrent one invocations (e.g. an agent/subagent orchestrator), the auto-updater could spawn many simultaneous global installs that deadlock on npm's locks, hang, orphan, and accumulate — never advancing the version, so the loop re-armed on every call.
- Mutual exclusion — a lock file (
~/.one/auto-update.lock) ensures at most one install runs at a time. - Self-healing — the lock is reclaimed after a 10-minute TTL, so a crashed/hung install can never block updates forever.
- Opt-out —
ONE_NO_AUTO_UPDATE=1disables background auto-updates entirely (for CI / shared agent hosts).
Full details: #148