OpenClaw merged an update reliability fix tonight for package work that happens after core activation. PR #153236, "fix(update): let package updates finish without an implicit deadline," changes how post-core package and Git Doctor work are allowed to settle.
The user-facing point is simple: update work that intentionally omits an explicit deadline should not fail merely because it inherited one from a surrounding phase.
The Update Path Being Repaired
OpenClaw's updater has to coordinate several different kinds of work. Core activation is the visible center of the flow, but package updates, npm packing, runtime admission, Git Doctor activation checks, and plugin-related follow-up work can continue around it.
Before this repair, some of that follow-up could run under an implicit deadline even when the specific package work did not set one. That creates an awkward class of failures: the main update path can be correct, but related package work is cut off by a deadline it did not ask for.
PR #153236 clarifies the behavior by keeping explicit deadlines meaningful while allowing omitted-deadline package work to finish. The change also updates documentation around post-core plugin work deadlines, so the behavior is easier for operators and maintainers to reason about.
What Stays The Same
The fix is deliberately narrow. It does not remove deadline enforcement across the update system. It keeps existing assertions for explicit deadlines, commands, and activation behavior.
The important distinction is between these two cases:
- Work with an explicit deadline should still obey that deadline.
- Package or Git Doctor work with no explicit deadline should not receive an accidental one from a broader update phase.
That separation is useful for real OpenClaw installations, where updates may include core packages, companion packages, plugin work, local activation checks, and diagnostics. Operators want timeouts where they are intentional, not where they are inherited by accident.
Why Operators Should Care
False update failures are expensive. They make an install look unhealthy even when the underlying repair path or package operation is doing the right thing. They also complicate support, because a deadline error can mask the actual state of the update.
This PR reduces that ambiguity. If package work needs a deadline, it can have one. If it omits a deadline, OpenClaw now treats that omission as part of the policy instead of filling the gap with inherited timing.
Verification
The PR body says the prior production owner failed both omitted-deadline cases, while the candidate passed all four deadline and activation cases. It also notes extracted npm packing and runtime admission tests, plus coverage for omitted Git Doctor work deadlines.
This is a reliability story more than a flashy release note. But for users who run OpenClaw as infrastructure, cleaner update semantics matter. The updater should fail loudly when something is actually wrong, and stay patient when follow-up package work is still legitimately finishing.